“Pull my latest audit and list the top three opportunities by impact divided by effort.”
Then ask the agent to inspect the repository and map each opportunity to the files or templates that need changes.
SearchSignal is the SEO brain your models query from Cursor, Claude, Windsurf, VS Code, ChatGPT, and custom agents. The UI remains available, but the agent can retrieve the workspace without opening it again.
The examples below use a placeholder token. The authenticated Connect AI screen should remain the source of truth for the exact current config.
{
"mcpServers": {
"searchsignal": {
"command": "npx",
"args": [
"-y",
"https://searchsignal.pro/mcp/searchsignal-mcp-1.0.1.tgz"
],
"env": {
"SEARCHSIGNAL_TOKEN": "YOUR_TOKEN"
}
}
}
}{
"mcpServers": {
"searchsignal": {
"command": "npx",
"args": ["-y", "https://searchsignal.pro/mcp/searchsignal-mcp-1.0.1.tgz"],
"env": { "SEARCHSIGNAL_TOKEN": "YOUR_TOKEN" }
}
}
}{
"mcpServers": {
"searchsignal": {
"command": "npx",
"args": ["-y", "https://searchsignal.pro/mcp/searchsignal-mcp-1.0.1.tgz"],
"env": { "SEARCHSIGNAL_TOKEN": "YOUR_TOKEN" }
}
}
}curl https://searchsignal.pro/api/mcp/v1/tools \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json"Use the authenticated Connect AI area. Rotation invalidates the old credential and refreshes the generated configs.
Use MCP for supported clients. Use Bearer authentication when the model or automation calls the HTTP API.
Start with the latest audit, top opportunities, a keyword exploration, or a workspace pack for a project.
A strong first prompt asks for the evidence, a priority order, and a delivery format the agent can use immediately.
Then ask the agent to inspect the repository and map each opportunity to the files or templates that need changes.
Follow with a page outline and internal-link plan based on the current project context.
Use the compact briefing as the starting context for strategy, implementation, or a client-facing plan.
This closes the gap between SEO analysis and the environment where changes can actually be made.
Create a free account or sign in, then open the Connect AI area in the authenticated app. The product generates client-specific configuration from the active token.
The product is designed around one active token that can be used across the supported MCP and HTTP client configurations. Rotate the token when you need to invalidate the previous credential.
No. The published connection path uses an npx-compatible package URL for major MCP clients, so setup does not require cloning the SearchSignal MCP repository.
Treat the token like an API key. Keep it in the environment or secure client configuration, avoid committing it to a repository, and rotate it if it is exposed.
SearchSignal turns connection into a product advantage: one authorized workspace can serve MCP clients and authenticated HTTP agents without forcing the user back into another tab.
Create a free account, issue the token, and connect SearchSignal to the AI client you already use every day.