Grok Dropspace get_batch_launch_analytics
How to: Grok Dropspace get_batch_launch_analytics
Add Dropspace to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"dropspace": {
"type": "http",
"url": "https://api.dropspace.dev/mcp"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something get_batch_launch_analytics does. Grok lists the server's tools on connect and calls get_batch_launch_analytics itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Dropspace's identifier in your config matches the one above exactly.
Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs
Set these first
Dropspace will not start until these are set, so get_batch_launch_analytics never becomes available.
-
DROPSPACE_API_KEY -
DROPSPACE_API_URL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 10 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.