Guides
MCP Integration
Configure Claude Desktop and other MCP clients to use Seemor
MCP Integration
The Seemor API uses the Model Context Protocol (MCP), which means it works natively with any MCP-compatible client.
Claude Desktop
Add this to your Claude Desktop MCP configuration (claude_desktop_config.json):
{
"mcpServers": {
"seemor": {
"url": "https://api.seemor.ai/api/mcp",
"headers": {
"Authorization": "Bearer sk_seemor_YOUR_KEY"
}
}
}
}After restarting Claude Desktop, the Seemor tools will appear in the tools menu. You can ask Claude things like:
- "Find me a quiet Italian restaurant in Soho"
- "What's the dining scene like in Shoreditch?"
- "Look up Dishoom and tell me what people love about it"
Other MCP clients
Any client that supports the MCP HTTP+SSE transport can connect to Seemor. The configuration pattern is the same:
- Endpoint:
https://api.seemor.ai/api/mcp - Protocol: JSON-RPC 2.0
- Authentication:
Authorization: Bearer sk_seemor_YOUR_KEYheader - Transport: HTTP POST with SSE response
Using without an MCP client
You can call the API directly via HTTP. Every request is a POST with a JSON-RPC 2.0 body:
curl -X POST https://api.seemor.ai/api/mcp \
-H "Authorization: Bearer sk_seemor_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "find_restaurant",
"arguments": { "name": "Barrafina", "city": "London" }
}
}'See the Quickstart for a complete walkthrough.
Troubleshooting
Tools not appearing in Claude Desktop:
- Verify the URL is exactly
https://api.seemor.ai/api/mcp - Check that your API key starts with
sk_seemor_ - Restart Claude Desktop after changing the config
Authentication errors (401):
- Verify your key hasn't been revoked at app.seemor.ai/developer
- Check the
Authorizationheader format:Bearer sk_seemor_...(note the space after "Bearer")
Rate limit errors (429):
- Free tier: 100 requests/minute, 2,000/day
- See Rate Limits for details