AI visibility API and MCP server
Everything in Signal is available outside the dashboard. A REST API covers brands, prompts, competitors, analytics, citations, query fan-out, runs, and opportunities, and an MCP server lets Claude, ChatGPT, Claude Code, Codex, Cursor, or VS Code read your data and manage prompts directly.
$ claude mcp add --transport http signal https://app.signal.metricshive.com/api/mcpQUERY · REST API
$ curl https://app.signal.metricshive.com/api/v1/brands \ -H "Authorization: Bearer $SIGNAL_API_KEY"
What You Can Do
1Issue a key, or sign in
Create an organization API key, read-only or read-write, optionally limited to some brands and given an expiry. MCP clients can also just sign in from a browser.
2Call it from code
Send plain HTTP requests from any language to list brands, pull analytics, or create prompts.
3Ask your assistant
Connect over MCP and ask 'What are some AEO opportunities for my brand?' using your real tracking data.
Data You Can Act On
- Analytics
- Visibility, share of voice, sentiment, position, citations, per-model, prompt, and query fan-out metrics.
- Runs
- Every prompt evaluation, with the full response and its mention assessments.
- Prompts, competitors, and brands
- Manage the setup behind your tracking programmatically.
- Opportunities
- The latest generated recommendations for a brand.
- MCP tools
- Read tools like get_analytics, get_citations, and get_query_fanout, and write tools for creating and updating prompts.
Use Cases
- Pipe AI visibility into a warehouse or BI tool alongside SEO and revenue data.
- Let an AI assistant investigate why a prompt lost visibility and draft the fix, using your real data.
- Keep prompts and competitors in sync across your brands from a script.
Why Signal
Included on every plan
API and MCP access come with every Signal plan, at no extra cost.
Scoped access
Keys can be read-only and limited to some brands. An MCP client is only offered the tools its key allows, and no MCP tool deletes data or changes billing.
A published OpenAPI spec
The full spec is public, so you can generate a client in your language or load it into your API tool.
Related Guides
Related Features
All Features- Audits and reportingAn overview dashboard, on-demand audits you can compare, chart exports, and an API for your own BI.
- Prompt trackingSuggested from your website, tagged and organized, with every AI answer kept for you to search and inspect.
- OpportunitiesContent to create, pages to refresh, and sources to pitch, generated from your own visibility and citation data.
Frequently Asked Questions
Something we didn't cover? Email us at signal@metricshive.com.
Does Signal have an API?
Yes. Signal serves a REST API at https://app.signal.metricshive.com/api/v1 with Bearer-token authentication, and publishes its OpenAPI spec at /api/v1/openapi.json.
Which AI clients work with Signal's MCP server?
Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code, and OpenCode have documented setup, and other clients that support remote MCP servers over HTTP work the same way. Sign in from the client, or send an API key as a bearer token.
Do I need an API key to use MCP?
No. Most clients connect by signing in from a browser, and the connection then acts as you. Use an API key for a client that can't open a browser, or to give a client less access than you have.
Is there an SDK?
Not yet. The API is plain HTTP and JSON, so any language's HTTP client works, and the OpenAPI spec can generate a typed client.
Start winning AI search today.
Start tracking your brand in minutes. Plans start at $49/mo.
- Self-serve
- Unlimited seats
- API and MCP access
Need a custom plan? Talk to Sales.