Documentation
3meel.ai exposes your knowledge bases through the Model Context Protocol (MCP) for AI clients (Claude, Cursor, OpenClaw, etc.) and through the 3meel CLI for terminals, scripts, and CI. Both use the same account, API keys, and data.
This page focuses on MCP: API keys, connection URLs, available tools, and errors. For install, auth, and shell workflows, open the CLI documentation.
CLI and MCP — which one?
Pick the interface that matches how you work. You can use both.
| Use case | Use | Details |
|---|---|---|
| IDE or chat assistant | MCP | Connect once with an API key URL. Tools run inside the assistant (see sections below). |
| Terminal, automation, CI | CLI | Same KBs and queries; optional --json for agents. 3meel mcp can print MCP URLs and config snippets. |
MCP is keyed by API keys. CLI uses your account session (email/password login) for dashboard parity; MCP-style access still uses API keys for 3meel mcp url / config.
Authentication
All MCP requests are authenticated using API keys. Pass your key as part of the MCP endpoint URL:
https://mcp.3meel.ai/mcp/{your-api-key}Account-scoped keys grant access to all your knowledge bases. Use the /mcp/unified/{apiKey} endpoint.
KB-scoped keys grant access to a single knowledge base. Use the /mcp/{apiKey} endpoint.
Generate keys from the API Keys page in your dashboard.
MCP Configuration
For Claude Desktop, add 3meel through Connectors and paste your MCP URL as a custom connector.
https://mcp.3meel.ai/mcp/unified/YOUR_API_KEYClaude Desktop should use Settings > Connectors > Add custom connector with the URL above. Cursor and other MCP clients can still use JSON config blocks from MCP configuration (logged in). From the terminal, 3meel mcp url can generate a connector-ready URL if you set THREE_MEEL_API_KEY.
Available Tools
The MCP server exposes two official tools. The dashboard playground also includes a local convenience action for listing knowledge bases, but that helper is not part of the MCP server itself.
Queries a knowledge base with a natural language question. Returns an answer with citations referencing specific pages and sections of source documents.
Parameters
queryknowledgeBaseIdformattext or json. Defaults to text.Example Response
{
"answer": "The study found a 23% improvement in retrieval accuracy...",
"citations": [
{
"documentName": "research-paper.pdf",
"pageNumber": 5,
"pageEnd": 7,
"sectionTitle": "Results and Discussion",
"citationUrl": "/view/doc_xyz?page=5"
}
],
"documentsSearched": 4
}Lists documents available to the authenticated MCP server context. KB-scoped keys return documents from one knowledge base; account-level keys return documents grouped across all accessible knowledge bases.
Parameters
None
Example Response
{
"knowledgeBases": [
{
"id": "kb_abc123",
"name": "Research Papers",
"documents": [
{
"id": "doc_xyz",
"name": "research-paper.pdf",
"status": "complete",
"pageCount": 24,
"createdAt": "2026-03-20T10:05:00Z"
}
]
}
],
"totalDocuments": 1
}Error Codes
The MCP server returns standard HTTP status codes. Tool calls may also return error messages in the MCP response payload.
| Code | Status | Description |
|---|---|---|
401 | Unauthorized | Invalid or missing API key. Check that your key is correct and active. |
403 | Forbidden | API key does not have access to the requested knowledge base. |
404 | Not Found | Knowledge base or document not found. Verify the ID is correct. |
429 | Rate Limited | Too many requests. Wait before retrying. Free tier is limited to 100 queries/month. |
500 | Server Error | Internal server error. If this persists, contact support. |
Rate Limits
Per-key rate limit: 60 requests per minute. Monthly query counters reset on the 1st of each month.
See the pricing page for full plan details.