Prepare the workspace
Add the domain, connect Search Console if relevant, and run or save the research Claude should be able to retrieve.
SEO MCP for Claude Desktop and Claude Code
Give Claude a live SEO workspace—not a stale briefing.
SearchSignal provides current project evidence through MCP so Claude can analyze, plan, write, or code from the same audits, keyword research, competitor context, and priorities your team sees.
MCP connectionOne SearchSignal tokenDashboard optional after setup
01 · Source-awareKnow where the evidence came from.Measured performance, crawl findings, licensed metrics, and saved research remain distinguishable.
02 · Project-scopedKeep context attached to the workspace.Domains, audits, lists, priorities, and history stay connected instead of becoming another export.
03 · Agent-deliveredCall the workspace through MCP or HTTP.Use the same authorized evidence in Cursor, Claude, ChatGPT, Windsurf, VS Code, and custom agents.
04 · Human-reviewableInspect the decision before it ships.The interface remains available while the agent handles retrieval, synthesis, and handoff.
Why this integration
Claude is strongest when the context is current, structured, and scoped to the task.
A long pasted report consumes context and becomes stale. SearchSignal lets Claude request the specific workspace evidence it needs—such as the latest audit, top opportunities, one keyword exploration, or a compact project pack—at the moment the task begins.
- Retrieve current audits and prioritized opportunities
- Explore keyword intent, metrics, SERP context, and ideas
- Bring competitor, ranking, backlink, and project context into the conversation
- Request a compact workspace pack before strategy or implementation
- Keep the SEO evidence close to the environment where the work will happen
Generic Claude Desktop MCP example
{{
"mcpServers": {{
"searchsignal": {{
"command": "npx",
"args": [
"-y",
"https://searchsignal.pro/mcp/searchsignal-mcp-1.0.1.tgz"
],
"env": {{
"SEARCHSIGNAL_TOKEN": "YOUR_TOKEN"
}}
}}
}}
}}See the connection workspace
Configure Claude, verify access, and start with evidence.
Use one SearchSignal credential for the MCP connection, inspect recent authorized access, and copy the exact client configuration from the authenticated workspace.
Interactive product screen · illustrative dataInspect Connect AI →
Setup
Connect Claude in three deliberate steps.
Generate the Claude config
Create the token and use the Claude Desktop or Claude Code setup shown in the authenticated Connect AI area.
Request a scoped pack
Ask Claude for the specific audit, keyword, opportunity, or workspace context needed for the current job.
The authenticated SearchSignal Connect AI page should remain the source of truth for exact client paths and configuration syntax. AI clients change their settings interfaces over time.
High-value use cases
Use live SEO context where it creates leverage.
Connection alone is not the product. The value comes from asking the model to retrieve evidence and produce an action that fits the environment.
SEO strategy
Synthesize the latest audit, rankings, keyword targets, and competitor gaps into a clear quarterly or sprint plan.
Content briefs
Turn live search research into differentiated briefs with intent, entities, questions, internal links, and conversion goals.
Claude Code implementation
Retrieve the evidence, inspect the repository, and translate the plan into specific components, routes, content files, and tests.
Executive summaries
Explain the few changes most likely to matter, with supporting evidence and plain-language rationale.
Competitive positioning
Use search gaps to identify the category, integration, comparison, and solution pages the product should own.
Recurring reviews
Create a consistent weekly audit and ranking review prompt without rebuilding the project context every time.
Prompt library
Start with work that would normally require several tabs.
These prompts combine SearchSignal context with the strengths of Claude.
“Give me a workspace_pack for example.com. Summarize current health, momentum, biggest gaps, and the next five actions.”
“Combine the latest audit, Search Console movement, and saved keyword targets into a 30-day implementation plan with dependencies.”
“Explore the target keyword, compare the SERP pattern, and create a brief that demonstrates the product instead of repeating generic advice.”
“Use the SearchSignal evidence and inspect this repository. Implement the highest-value fix with a verification checklist.”
Integration FAQ
Connecting SearchSignal and Claude.
The product's published connection options include both Claude Desktop and Claude Code.
SearchSignal is designed around one active MCP/API token with client-specific configuration generated in the Connect AI area.
Yes. Keyword exploration and workspace packs are core examples, and the wider product includes keyword ideas, bulk analysis, and saved lists.
The UI remains useful for project setup and review, but the product is intentionally designed so many teams can stay in Claude after connection.
The product behind the page
Give Claude a live project workspace.
MCP lets Claude Desktop and Claude Code retrieve current audits, research, opportunities, and workspace context from the environment where reasoning happens.
01Add one MCP server.
02Use project-aware prompts.
03Move from analysis to a concrete handoff.
Connect once. Ask anywhere.
Give Claude the SEO context it should have had from the start.
Create a free SearchSignal workspace, generate the exact Claude configuration, and ask for your first live project briefing.