MCP Server — Use Your Bot as an AI Tool
Your knowledge base is valuable in more places than your website. MCP Server exposes it as a first-class tool so Claude, ChatGPT and Cursor agents can query, extend and ingest into it directly.
Sound Familiar?
AI Agents Can't Access Your KB
You have a world-class knowledge base, but Claude and ChatGPT have no way to reach it during a chat. Agents guess or refuse.
Manual Copy-Paste Workflow
Engineers paste your docs into an AI agent one file at a time. It works, but it's slow and breaks the moment the docs update.
No Developer API Standard
Building a custom REST wrapper for every AI client is duplication. MCP is the industry-aligned standard — use it instead.
What You Get
OpenAI-Compatible Manifest
GET /v1/mcp/manifest returns the tool catalogue in the format Claude Desktop, Cursor and any OpenAI-compatible agent already understands.
4 Tools Exposed
query_knowledge_base, list_documents, add_knowledge, ingest_url — enough to let an agent both read and contribute back.
X-Api-Key Auth
Standard header-based auth. Each key scopes the agent to a single site. Revocable, auditable, no OAuth dance required.
Works with Claude, GPT, Cursor
Tested against Claude Desktop, OpenAI's function-calling API, and Cursor's MCP client. Adding the server is a config-file edit.
Tenant-Isolated
site_id must match the key's scope; cross-tenant requests are blocked. Multi-client agencies keep their customers' data separate at the agent layer too.