
Shruwd Mcp
io.github.ilprPublished by GitHub account ilprv0.1.11Updated Nov 3, 2026
Set up a brand, read its AI-search visibility, and act on diagnostic findings.
Overview
Shruwd MCP lets an assistant set up a brand, track prompts and competitors, and read how the brand appears in AI-generated answers.
- What you can do
- Read workspace plan, entitlements, usage and brands
- Create, update, list and archive brands, and manage the prompts asked of each AI engine
- Manage the brand and competitor entities with the aliases that count as mentions
- Run measurements, list cycles, and read visibility, share of voice and crawler activity
- Inspect cited sources, individual answers, and diagnostic findings with fixes
- Draft suggested prompts and competitors, and create an ingest token for server logs
- When to use it
- Useful when you want an assistant to set up or maintain a brand's AI-search visibility tracking, review which prompts and competitors are monitored, and work through diagnostic findings without opening the dashboard.
- Requirements
- Either the hosted endpoint at shruwd.io/mcp with an OAuth sign-in, or the local npm package shruwd-mcp run via npx with Node.js. A Shruwd account and an API key from the dashboard, supplied as SHRUWD_API_KEY; SHRUWD_API_URL optionally overrides the API base URL. Network access to Shruwd.
Installation
In SourceWeft
- Open Shruwd Mcp in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.ilpr%2Fshruwd-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"shruwd": {
"type": "http",
"url": "https://shruwd.io/mcp"
}
}
}README
shruwd-mcp
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.
Hosted, no install
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:
Setup for each app: shruwd.io/docs/api/mcp-server.
Claude Desktop
claude_desktop_config.json:
Claude Code
Cursor
.cursor/mcp.json:
Tools
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.
Environment
Source: README.md at commit cb42186
Tools
0Version history
7- v0.1.11LatestNov 3, 2026
- v0.1.9Oct 19, 2026
- v0.1.8Oct 15, 2026
- v0.1.7Oct 15, 2026
- v0.1.6Sep 30, 2026
- v0.1.5Sep 22, 2026
- v0.1.2Sep 20, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts