MCP server
MCP server. Connect Claude Code, Cursor or any MCP client to VectraSEO over Streamable HTTP or the npx stdio bridge, with the full tool list and safety model. This chapter is part of the VectraSEO field manual: it names the exact endpoints, credentials, checks and response fields the hosted service uses, so you can wire the same capability into your own pipeline and verify it against the live API.
Drive VectraSEO from an AI assistant
VectraSEO ships a Model Context Protocol server, so an assistant can create, onboard and manage projects directly. Same account key, same permissions as the Provisioning API.
https://api.vectraseo.com/mcpConnect
claude mcp add --transport http vectraseo \ https://api.vectraseo.com/mcp \ --header "x-api-key: vsak_..."
Any client that speaks Streamable HTTP can point at that URL with an x-api-key (or Authorization: Bearer) header. For clients that can only launch a stdio subprocess, run npx -y @vectraseo/mcp with VECTRASEO_API_KEY set — a zero-dependency bridge to the same endpoint.
Tools
Safety
Tool calls run through the same REST API with the same credential, so an assistant can never do anything the API would refuse — the scope check, plan gate and ownership check all run in their usual place. Tools that spend budget or write to your live site are flagged destructiveHint so your client can prompt first, and the server tells the assistant to confirm with you before calling them. No tool can delete a project, and no tool can manage API keys — including its own, so a leaked key cannot perpetuate itself.
Can't find what
you're looking for?
Reach out to the team. We answer every email and we read every bug report.