How to connect SpyFu MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"spyfu": {
"command": "npx",
"args": ["-y", "<server-package-name>"],
"env": {
"SPYFU_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://github.com/AlexanderCord/spyfu-mcp-server
// Check the server's README for the exact "command" and required env vars.Some MCP servers require an API key. Check the source page for setup: github.com/AlexanderCord/spyfu-mcp-server.
Does SpyFu MCP cost extra?
The SpyFu MCP server is community-built — free to run, but you still pay for your SpyFu subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your SpyFu account still needs whatever plan is required to access the data the MCP server queries.
- Trade-off: zero MCP cost, but no guarantee it'll keep working when SpyFu changes their UI or API.
SpyFu subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| Basic | $39 | $29 |
| Pro + AI | $119 | $89 |
| Team / Agency | $249 | $187 |
Source: spyfu.com/pricing. Scraped 2026-05-19.
SpyFu also publishes a REST API
SpyFu publishes an API, but per-tier gating wasn't extracted automatically.
See SpyFu API pageWhat you can do with SpyFu from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What keywords moved this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe SpyFu data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's SpyFu account
- Multi-account workflows without context-switching the SpyFu UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage SpyFu data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production SpyFu safe
Limits and gotchas
- Community MCP — not maintained by SpyFu. Check the README and last-update date before depending on it.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Auth flow: MCP servers usually inherit the underlying API auth method (both). Expect to configure that on first install.
- Rate limits: MCP calls count against your underlying SpyFu API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Limited agent integration despite community MCP. SpyFu has documented public API and a working community MCP server, but lacks official MCP hosting on its own domain and any OpenAPI specification to standardize agent access. The missing OpenAPI spec and absence of webhooks or structured output support make workflow automation friction-heavy compared to modern agent-first tools.
Scored 2026-05-19 by Joonas (TMB).
SpyFu MCP & API FAQ
Is the SpyFu MCP server official?+
Can I use the SpyFu MCP with Cursor or Codex?+
Does SpyFu have a public API?+
Sources
- SpyFu official site: https://www.spyfu.com
- MCP server page: https://github.com/AlexanderCord/spyfu-mcp-server
- API docs: https://developer.spyfu.com/
- Pricing source: https://www.spyfu.com/pricing (scraped 2026-05-19)
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

