CU
Cursor
Give Cursor access to audits, opportunities, keyword intelligence, and project packs while it works in your repository.
MCPMCP + HTTP integrations
Put live SEO data inside the AI you already use.
One SearchSignal token supports MCP clients and authenticated HTTP agents. Choose the setup for your tool, paste the generated config, and keep working in the environment you know.
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.
CL
Claude Desktop & Code
Use SearchSignal as live context in Claude conversations and coding workflows without rebuilding the SEO brief.
MCPGPT
ChatGPT & Custom GPTs
Use the Bearer HTTP API in your own actions, connectors, or agent workflows when MCP is not the chosen path.
HTTP APIWS
Windsurf
Keep SEO research available while the agent inspects, plans, and edits the project inside Windsurf.
MCPVS
VS Code & Copilot workflows
Attach SearchSignal to compatible MCP tooling around VS Code so search evidence stays close to the code.
MCPAPI
Any HTTP agent
Use Bearer authorization and the SearchSignal API base when you are building your own agent, automation, or backend workflow.
HTTP APITwo connection paths
MCP when the client supports it. HTTP everywhere else.
SearchSignal separates the workspace from the client. The token authenticates the user; the delivery path adapts to the model or environment.
- One account and token management surface
- Client-specific configs generated after sign-in
- Zero-install npx package path for major MCP clients
- Bearer authorization for custom models and HTTP agents
- Rotate or revoke a token when the environment changes
A better first session
Connect, then ask a question worth answering.
The fastest way to understand the product is to use the agent to retrieve a real project briefing and turn it into a concrete plan.
Audit triage
“Pull my latest audit. Rank open issues by expected impact divided by effort.”
Keyword exploration
“Explore ‘SEO MCP server’ and return intent, opportunity score, winning page type, and a content angle.”
Repository handoff
“Give me a workspace pack, inspect this repository, and create a file-by-file implementation plan.”
The product behind the page
The integration is the commercial wedge.
SearchSignal is strongest when the customer can keep working in Cursor, Claude, ChatGPT, Windsurf, VS Code, or a custom agent after one connection.
01Prioritize first-party setup paths.
02Use one credential model.
03Keep the dashboard optional after setup.
Connect once. Ask anywhere.
Connect the SEO workspace to your strongest model.
Choose your client, generate the exact config after sign-in, and let the agent retrieve its first live SearchSignal briefing.