Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@shruwd-mcp Check if my brand is mentioned in AI answers and list any findings."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A local MCP server for Shruwd. It lets an AI agent — Claude Desktop, Claude Code, Cursor, anything that speaks MCP — set up a brand, add the prompts and competitors to track, read how the brand appears in AI-generated answers, and act on the diagnostic findings.
You need an API key from the Shruwd dashboard (Account → API keys). The key is bound to
one workspace and reaches your brands in it: every brand if you own the workspace, the
brands you are a member of otherwise. It acts with your role on each brand: reads need
viewer, writes editor, minting an ingest token admin; creating or archiving a brand
needs the owner. To work across several workspaces, mint a key in each and add one
server entry per workspace.
The same tools run at https://shruwd.io/mcp (Streamable HTTP). In Claude.ai, ChatGPT
or Grok, add that URL as a custom connector and sign in with your Shruwd account; no
key needed. A client that takes a header can send a key instead:
claude mcp add --transport http shruwd https://shruwd.io/mcp --header "Authorization: Bearer sh_live_…"Setup for each app: shruwd.io/docs/api/mcp-server.
Related MCP server: BranderUX MCP
claude_desktop_config.json:
{
"mcpServers": {
"shruwd": {
"command": "npx",
"args": ["-y", "shruwd-mcp"],
"env": { "SHRUWD_API_KEY": "sh_live_…" }
}
}
}claude mcp add shruwd -e SHRUWD_API_KEY=sh_live_… -- npx -y shruwd-mcp.cursor/mcp.json:
{
"mcpServers": {
"shruwd": {
"command": "npx",
"args": ["-y", "shruwd-mcp"],
"env": { "SHRUWD_API_KEY": "sh_live_…" }
}
}
}Tool | Does |
| Plan, entitlements, usage, brands. Start here. |
| Brands. Creating one also creates its self entity and first measurement. Creating and archiving need |
| The questions asked of each engine every cycle, and the page on your site that should answer each. |
| The brand and its competitors, with the exact aliases that count as a mention. |
| Measure now; watch the cycle. Results arrive over the following hours. |
| Mention rate and share of voice with intervals, now and at every cycle close; verified AI-crawler activity. |
| The latest individual answers: whether the brand was named and at what rank, the competitors named, the pages cited. Narrows to one prompt (a finding's |
| Competitors the answers named that the brand does not track yet. |
| Drafts ten prompts and up to six competitors from the homepage. Nothing is saved until they are added with the usual tools. |
| Diagnoses with a specific fix; mark a fix applied to start the recheck. Capped plans return the rest as a |
| The token and endpoint for shipping server logs. Needs |
Every tool returns exactly what the API returns. Metrics are never bare numbers: each is
a point estimate with its 95% interval and n, or an explicit insufficient_data state,
which the tool descriptions tell the agent not to read as zero. Plans that cap visible
findings report the remainder as a locked count rather than hiding that it exists.
Variable | |
| Required. |
| Optional. Defaults to |
This server cannot be deployed
AI visibility analytics for brands across citations, prompts, competitors, research, and reports.
Track your brand's visibility in ChatGPT, Perplexity, Claude, Gemini, Grok and DeepSeek answers.
Track brand visibility in ChatGPT, Gemini and Google AI answers: competitors, cited sources, checks.
Track and manage how your brand appears in AI answers: rank, mentions, sentiment, share of voice.
