MCP Integration
KnowledgeFlowDB provides an MCP (Model Context Protocol) server with 150+ tools for AI agent integration. Agents can query, search, write, and analyze data in KnowledgeFlowDB through the standardized MCP protocol.
What is MCP?
The Model Context Protocol is an open standard for connecting AI models to data sources and tools. KnowledgeFlowDB's MCP server lets any MCP-compatible AI agent (Claude, GPT, custom agents) interact with your knowledge graph.
MCP Marketplace
The MCP Marketplace provides a discovery and management interface for MCP servers, including KnowledgeFlowDB's 150+ tools.
Features:
- Browse and search available MCP servers
- Enable/disable servers for your wallet
- View tool documentation and schemas
- Integrated wallet authentication and x402 payment
Connecting to the MCP Server
MCP Server URL
https://kfdb-mcp-server-2dbp4scmrq-uc.a.run.app/mcp
Tool Profiles
Tools are organized into profiles to manage context window usage:
| Profile | Tools | Use Case |
|---|---|---|
minimal | 40 | Quick queries (default) |
development | 70 | Active development |
research | 85 | Research cycles, A/B experiments |
full | 150 | No filtering — all tools available |
Claude Desktop Configuration
Add to your Claude Desktop claude_desktop_config.json:
{
"mcpServers": {
"knowledgeflow-db": {
"command": "npx",
"args": ["-y", "@nickydata/mcp-client"],
"env": {
"KFDB_API_BASE_URL": "https://api.knowledgedataflow.org/api/v1",
"KFDB_BEARER_TOKEN": "YOUR_BEARER_TOKEN",
"KFDB_DERIVE_SESSION_ID": "YOUR_DERIVE_SESSION_ID",
"KFDB_DERIVE_KEY": "YOUR_DERIVE_KEY_HEX"
}
}
}
}
For interactive docs usage, you do not need to set these manually. Sign in with Privy and the docs site establishes the bearer session and derive session for you.
Tool Categories
See MCP Tools for the complete tool reference organized by category.
Authentication
MCP tool calls use the same auth layers as the REST API:
- Primary hosted flow: Privy login, wallet challenge/verify, and sign-to-derive
- Programmatic flow: Bearer token plus derive session and derive key headers
- Legacy/internal compatibility:
X-Wallet-Addressonly where older tooling still expects it - Payments: x402 protocol for paid tool calls ($0.0005/call)
See Wallet Authentication for details.