How to connect ValueSERP 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": {
"valueserp": {
"command": "npx",
"args": ["-y", "<server-package-name>"],
"env": {
"VALUESERP_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://github.com/Incorporo/valueserp-googlesearch-mcp
// 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/Incorporo/valueserp-googlesearch-mcp.
Does ValueSERP MCP cost extra?
The ValueSERP MCP server is community-built — free to run, but you still pay for your ValueSERP subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your ValueSERP 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 ValueSERP changes their UI or API.
ValueSERP also publishes a REST API
ValueSERP publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with ValueSERP 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 ValueSERP 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 ValueSERP account
- Multi-account workflows without context-switching the ValueSERP UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage ValueSERP data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production ValueSERP safe
Limits and gotchas
- Community MCP — not maintained by ValueSERP. 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.
- OpenAPI spec is published — easy to validate which endpoints the MCP server actually exposes vs the full API surface.
- Rate limits: MCP calls count against your underlying ValueSERP API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Moderate agent-fit with community support. ValueSERP offers a public API with OpenAPI spec and a community MCP server, making it usable in Claude workflows, but lacks official MCP hosting, multiple SDKs, and structured outputs that would enable seamless agentic parsing. The missing native integrations and absence of webhooks limit real-time automation capabilities.
Scored 2026-06-07 by Joonas (TMB).
ValueSERP MCP & API FAQ
Is the ValueSERP MCP server official?+
Can I use the ValueSERP MCP with Cursor or Codex?+
Does ValueSERP have a public API?+
Does ValueSERP publish an OpenAPI / Swagger spec?+
Sources
- ValueSERP official site: https://www.valueserp.com
- MCP server page: https://github.com/Incorporo/valueserp-googlesearch-mcp
- API docs: https://trajectdata.com/serp/value-serp-api/
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.

