Skip to main content
The Attensira MCP server puts your visibility data inside the assistant you already work in. Instead of switching to the dashboard, reading a number, and carrying it back by hand, your assistant queries the workspace directly, then changes it — adding prompts, running automations — in the same conversation.

​
What MCP gives you that the dashboard does not

The dashboard shows you numbers. MCP lets an assistant read those numbers and act on them without you leaving the work you are doing. That closes the loop between noticing something and changing something. Concretely: while editing a pricing page, you can ask which prompts mention a competitor and not you, then add three new prompts covering the gap — one conversation, no tab switching. While reviewing a release, you can pull mention rate for the last 30 days, compare it against the previous window, and check whether the delta is statistically real before anyone writes it into a report. The server exposes 15 tools across four groups: find and measure (search, get_analytics, get_prompt, get_page), track (add_prompts, remove_prompt, add_competitor), automations (list_automations, get_automation, create_automation, run_automation, delete_automation), and agent (ask, get_session, get_account). Eight are read-only. Two are destructive: remove_prompt and delete_automation. Three spend credits: add_prompts, run_automation, and ask.
An assistant with your key can delete prompts and automations, and can spend credits. Treat the key as a workspace credential, not a read token.

​
How authentication works

You mint a key at app.attensira.com/settings/developer and send it as Authorization: Bearer atn_live_<32 hex>. The key is displayed exactly once, because only a hash is stored — Attensira cannot re-display it, and a lost key is replaced rather than recovered. The key names the workspace. No tool takes a workspace id, so there is nothing in a request that can be retargeted: a URL that cannot express a workspace cannot be pointed at someone else’s. To work across two workspaces, mint two keys and configure two server entries.

​
Where the server lives

The endpoint is https://mcp.attensira.com/mcp, and it speaks Streamable HTTP only. A client that speaks stdio alone cannot reach it directly and needs a bridge — see Connect a client. https://mcp.attensira.com/healthz is unauthenticated and answers without a key, which makes it a useful reachability check when a client is silent about why it failed.

​
Next steps

Connect a client

Copy-pasteable setup for Claude Code, Cursor, VS Code, Codex, ChatGPT, n8n and more.

Tool reference

All 15 tools, their arguments, and which ones cost credits.

Recipes

Worked prompts that get useful answers on the first try.
Something not working? Troubleshooting covers 401s, missing tools, revoked keys, empty results, and timeouts.