Knowledge bases over MCP
Knowledge bases you create under Knowledge Bases in the app are searchable over the Model Context Protocol — both by your deployed voice agents (wired automatically at deployment time) and by any MCP client you connect yourself (Claude, OpenAI-compatible clients, and others).
Authentication
Use an organization API key (created under Settings → API Keys, ela_ prefix) with either header:
X-API-Key: YOUR_API_KEYAuthorization: Bearer YOUR_API_KEY
Connecting
The MCP server speaks streamable HTTP. With Claude Code:
claude mcp add elacity-kb --transport http https://YOUR_MCP_SERVER_URL/mcp \
--header "X-API-Key: YOUR_API_KEY"Or in an mcpServers JSON config (Claude Desktop and compatible clients):
{
"mcpServers": {
"elacity-kb": {
"type": "http",
"url": "https://YOUR_MCP_SERVER_URL/mcp",
"headers": { "X-API-Key": "YOUR_API_KEY" }
}
}
}The exact endpoint URL and copy-paste snippets for your environment are shown in the Developer dialog on each knowledge base's detail page.
Tools
| Tool | Description |
|---|---|
list_knowledge_bases | Lists the knowledge bases your key can search (slug, name, description) |
search_knowledge_base | Semantic search over one knowledge base — pass knowledge_base (the slug) and a natural-language query, plus optional max_results |
Your API key scopes access to your organization's knowledge bases only.
Your deployed voice agents connect over a separate, automatically-wired route that exposes one dedicated
search_<slug>tool per linked knowledge base (so the agent queries a specific KB in a single call). That route is provisioned for you at deployment time and requires a platform token — the/mcpendpoint documented above is the one to use from your own MCP clients.