Make search intelligence callable.

Quickstart

Create a SearchSignal account, add a project, run or import the data you need, and issue a token from the authenticated Connect AI area. Use the generated client config rather than copying a token from screenshots or logs.

1. Create or sign in to a SearchSignal workspace.
2. Add the domain and optionally connect Google Search Console.
3. Run an audit or save the keyword and competitor research the agent will need.
4. Create an MCP/API token.
5. Paste the exact config for the selected client.
6. Ask for latest_audit, list_opportunities, explore_keyword, or workspace_pack.

Authentication

MCP clients receive the credential through the client configuration or environment. HTTP clients send the token using Bearer authorization.

Authorization: Bearer YOUR_TOKEN

Token lifecycle

• Create: issue the first token from the Connect AI screen.
• Rotate: invalidate the old credential and reveal a new one.
• Revoke: remove access when a client or environment should stop using the workspace.

MCP setup

For clients that support Model Context Protocol, SearchSignal uses an npx-compatible package path and the workspace token.

{
  "mcpServers": {
    "searchsignal": {
      "command": "npx",
      "args": [
        "-y",
        "https://searchsignal.pro/mcp/searchsignal-mcp-1.0.1.tgz"
      ],
      "env": {
        "SEARCHSIGNAL_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

HTTP API

Use the HTTP path for ChatGPT workflows, custom models, automations, and systems where MCP is not the chosen transport.

curl https://searchsignal.pro/api/mcp/v1/tools \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"

Call a tool

curl -X POST https://searchsignal.pro/api/mcp/v1/call \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "tool": "latest_audit",
    "arguments": {
      "project": "example.com"
    }
  }'

The final production docs should be generated from the live tool contract so endpoint paths, parameters, response shapes, and errors cannot drift from the backend.

Core tools

SearchSignal's product surface also includes keyword ideas, bulk analysis, domain exploration, competitor gaps, rank tracking, backlinks, content briefs, and AI writing. The live /tools response should remain the authoritative catalog of callable tool names.

Prompt patterns

Audit to implementation

Pull the latest audit for example.com.
Rank the open opportunities by expected impact divided by effort.
Then inspect this repository and create a file-by-file implementation plan.

Keyword to page strategy

Explore the keyword “SEO MCP server.”
Return intent, opportunity, SERP pattern, supporting terms,
and the page type most likely to satisfy the query.

Workspace briefing

Give me a workspace_pack for example.com.
Summarize current health, strongest traffic opportunities,
ranking momentum, and the next five actions.

Security

• Never commit tokens to source control.
• Do not expose full token values in browser analytics, server logs, screenshots, or support tickets.
• Rotate credentials after suspected exposure or when a shared environment changes ownership.
• Keep token issuance and storage server-side in the production app.
• Rate-limit and audit calls at the authenticated workspace boundary.
• Return only the project data the signed-in workspace is authorized to access.

Production documentation checklist

• Generate the tool catalog from the live MCP/API schema.
• Document request and response examples from real test fixtures.
• Publish stable error codes and retry guidance.
• Version the package and API contract deliberately.
• Add a changelog when tool names, arguments, or response shapes change.
• Keep client setup screenshots current as Cursor, Claude, Windsurf, and VS Code interfaces evolve.