Skip to content

Grok mcp Resource/errors/payload_too_large

How to: Grok mcp errors/payload_too_large

client:Grok transport:streamable-http resource:errors/payload_too_large

Add mcp to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.doc.cheap/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    errors/payload_too_large is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.

  3. 04

    If it does not appear, check that mcp is connected and that you are looking at its resources rather than its tools.

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

mcp will not start until these are set, so it never reaches Grok.

  • DOC_CHEAP_API_KEY
  • DOC_CHEAP_API_BASE

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.