AACSearch / guide
MCP for AI clients
Connect an AI client to the generated AACSearch tool server.
What the server does
The MCP server exposes tools generated from the public OpenAPI contract. Requests still use your API key and the same access controls and quotas. It is not a substitute for a search index or a way to bypass permissions.
Run from the repository
The generated package is private in this repository; these instructions do not assume a published npm package. With source access, from sdks/mcp:
npm ci
npm run buildConfigure your MCP client's local server command as node, with the absolute path to sdks/mcp/build/index.js as its argument. Use the stdio transport. Set credentials through the client's secret/environment configuration:
{
"API_BASE_URL": "https://api.aacsearch.com/v1",
"API_KEY_API_KEY_HEADER": "YOUR_API_KEY"
}A search key only authorizes search-scope operations. Administrative operations require a full key; approve writes deliberately in your AI client and use a test organization first. Never commit real credentials to an MCP configuration.
Verify the connection
Connect the client, list tools, then run a read operation allowed by your key. If authentication fails, check the base URL, key scope and collection restrictions. On 429, inspect quotas and retry timing. See keys, errors and the API reference for the underlying operations.