Configuring Remote MCP Tool in Grok Request

Example of configuring a Remote MCP Tool within the tools array of a Grok request.

GrokVerbatim
Code
{
  "tools": [
    {
      "type": "remote_mcp",
      "server_url": "[[your_mcp_server_url]]",
      "allowed_tools": ["[[tool_name_1]]", "[[tool_name_2]]"]
    }
  ]
}
Language

json

Explanation

This JSON snippet shows how to include a Remote MCP Tool configuration in the `tools` array of a request. It specifies the `server_url` and optionally `allowed_tools` to define which tools from the MCP server are accessible.

What it does and when to use it

This JSON configuration demonstrates how to set up a Remote MCP Tool within a Grok request. It requires the MCP server's URL and can optionally list specific tools to be made available to the model.

Why it works

The `tools` array is where Grok expects tool configurations. Specifying `type: "remote_mcp"` and providing the necessary parameters enables the integration.

When not to use it

When not using Remote MCP Tools or when configuring tools through a different mechanism.

Sources and credit

First seen on Subvolts Jul 20, 2026. Updated Sep 11, 2026. Spotted a problem? Tell us.

Where it shows up
Terms used

Model context protocol

Related in the PlaybookPlaybook →

The Playbook: reusable how-tos, prompts, configs and tips pulled out of the news.

Questions people ask

Which AI tools does this work with?
The sources used it with Grok.
Where did this come from?
xAI (xAI Docs: Guides). Subvolts collected, normalized and credited it; the link above opens the original.