SignalGap ships a Model Context Protocol (MCP) server. Connect it to Claude Desktop, Cursor, or any MCP client and ask "what should I do this week?" without opening the app. Read-only, runs locally, one config block.
read-only stdio local
The server reads from the same account-scoped data the web app uses. It never writes — approving actions, publishing posts, and launching ads still happen in the app, on purpose. Think of this as a window, not a remote control.
this_weeks_plan
Your prioritized action plan for the week — counter-ads, SEO fixes, content ideas — with status and totals.
list_competitors
The competitors SignalGap is monitoring, with domain and tier.
recent_changes
Competitor change events (SEO, pricing, tech, ads) from the last N days. Takes a days argument.
site_audit_summary
Latest site-audit results per owned domain: total findings and how many are critical.
1. Install dependencies
From your SignalGap checkout:
2. Find your account ID
The server scopes every query to one account. Grab your numeric account ID from the app URL or your account settings. You'll pass it as an env var.
3. Add it to your MCP client
In Claude Desktop, open claude_desktop_config.json (Settings → Developer → Edit config) and add a server entry:
Restart the client. You'll see the four SignalGap tools appear. The same block works in Cursor
(~/.cursor/mcp.json) and any other MCP-compatible client — only the config file path differs.
Test it from the terminal
"What's on my SignalGap plan this week, and which ones are highest priority?"
"Summarize what my competitors changed in the last 14 days."
"How many critical issues did my last site audit find?"
"Draft a reply to the most urgent counter-ad on my plan." (Claude reads the plan, you act in the app.)
Three competitors free forever. The MCP server ships with every account.