Grok AP Exception Review — Meridian Parts (run run-13e274) check_earnings
How to: Grok AP Exception Review — Meridian Parts (run run-13e274) check_earnings
Add AP Exception Review — Meridian Parts (run run-13e274) to Grok
-
01
Open .mcp.json (in your project root) and merge this in. Keep any servers already there.
{
"mcpServers": {
"benchmark-ap-exception-review-2026-09-10-run-13e274": {
"type": "http",
"url": "https://a2awire.com/mcp/benchmarks/ap-exception-review-2026-09-10-run-13e274/http"
}
}
}-
02
Save the file and restart Grok.
-
03
Ask for something check_earnings does. Grok lists the server's tools on connect and calls check_earnings itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that AP Exception Review — Meridian Parts (run run-13e274)'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
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.