Docs
Documentation
Connect your MCP client to khive in 30 seconds. Full service reference below.
Quick Start
Claude Code
~/.claude/settings.json{
"mcpServers": {
"khive": {
"url": "https://mcp.khive.ai/mcp",
"headers": {
"X-Api-Key": "sk_live_YOUR_API_KEY"
}
}
}
}Cursor
.cursor/mcp.json{
"mcpServers": {
"khive": {
"url": "https://mcp.khive.ai/mcp",
"headers": {
"X-Api-Key": "sk_live_YOUR_API_KEY"
}
}
}
}Any MCP Client
generic configServer URL: https://mcp.khive.ai/mcp
Transport: Streamable HTTP (MCP protocol)
Auth: X-Api-Key header with your API keyUnified Tool
All services are accessible through a single request tool using function call syntax:
// Single operation
request('memory.recall(query="project status")')
// Batch (parallel execution)
request('[memory.recall(query="notes"), task.next(), schedule.today()]')Each service also registers individual MCP tools (e.g., memory, know) with an action parameter.
Service Reference
memory.rememberStore a memory for later recall
memory.remember(content="Ship v1 by Friday", importance=0.9)
memory.recallSearch memories by semantic query
memory.recall(query="shipping deadlines", limit=5)
Data Isolation
Each API key maps to a unique tenant namespace. Your data is physically isolated:
Separate SQLite database per tenant
Separate embedding indices per tenant
No cross-tenant data access possible
API key authentication on every request
Service Availability
| Service | Free | Plus | Pro |
|---|---|---|---|
| memory | |||
| know | — | ||
| task | |||
| crm | — | ||
| schedule | — | ||
| areas | — | ||
| domains | — | — | |
| waves | |||
| inbox | |||
| messages | — | ||
| atoms | — | — | |
| agents | |||
| request (batch) | — |
Rate Limits
| Tier | Calls/day | Memories | Entities |
|---|---|---|---|
| Free | 100 | 1,000 | — |
| Plus | 5,000 | 50,000 | 10,000 |
| Pro | 50,000 | Unlimited | Unlimited |