Grokbot MCP server
Which MCP servers are Grokbot's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry nametools.grokbot/connectorsverified in the MCP registry
The registry name sits under grokbot.tools. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools6
- Server calls itselfgrokbot-tools
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 402 ms.
- Its tools do none of the product's use cases we checked: check your Linear tasks from Grok bot; add a custom MCP server to your bot.
- Checked on 6 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
- What an agent can do with it0 of 2 use cases
- Answeredmeasuring6 of the 7 daily checks it takes to print a share
- Median first answer381 ms
- Space in an agent's context≈ 1,705 tokensthe definitions of all its tools (6), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- cannot · check your Linear tasks from Grok bot
- not sure · find and add MCP connectors for your apps
- cannot · add a custom MCP server to your bot
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_connectorsSearch the grokbot.tools directory of MCP connectors and plugins for Grok Bot by name, service or category, with optional filters (Grok Bot test status, install method, auth type). Returns compact summaries with the install method, auth…
get_connectorGet the full public record for one published connector by its slug (the last part of https://grokbot.tools/connectors/{slug}): summary, install method with step-by-step instructions and sources, MCP URL (null for built-in plugins), auth…
list_connectorsPage through every published connector in the grokbot.tools directory, alphabetically, with the same optional filters as search_connectors. Returns compact summaries plus the total, the categories in use (first page), and a next_cursor to…
list_requestsList the grokbot.tools wishlist: apps people want connected to Grok Bot, sorted by on-site votes or by newest. Each item has its status (requested, claimed, live), on-site vote count, the labeled seed signal ('X buzz (seed)', mentions…
get_requestGet one wishlist request by slug (the last part of https://grokbot.tools/requests/{slug}): status, on-site votes, the labeled seed signal, description, public sources (links to the posts it came from), the linked connector if one exists…
how_to_add_connectorExplains how an app gets into Grok Bot: built-in plugins (Connect apps in the sidebar), custom MCP servers (you ask the Bot in chat to add a URL; must be public HTTPS using streamable HTTP or SSE), and the browser-only route when neither…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"connectors": {
"type": "http",
"url": "https://mcp.grokbot.tools/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http grokbot https://mcp.grokbot.tools/mcpclaude.ai, ChatGPT and other clients: add https://mcp.grokbot.tools/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.