MCP Integrations

MCP connects Grok to other apps you trust (issue trackers, Blender, and similar tools).

After you ship a walkthroughOnly needed when connecting other apps
Modular connectors
MCP plugs extra apps into Grok.

What MCP is

MCP (Model Context Protocol) lets Grok call tools from another program—issue trackers, Blender, browsers, internal APIs. Built-in tools still work; MCP adds more.

Steps: add → check → use

  1. Get a server — follow that product’s MCP install docs (often npx, uvx, or a binary).
  2. Register it with the CLI or config (examples below).
  3. Check it is healthy — /mcps in Grok, or list/doctor CLI commands when available.
  4. Use plain English — e.g. “Create a Linear issue for this bug” if Linear MCP is connected. Grok finds the tools; you rarely type raw tool IDs.
# Common CLI shape (names may evolve—check /docs if a flag differs)
grok mcp add <name> -- …     # register a server
grok mcp list
grok mcp doctor              # diagnose startup failures when available
# In TUI: /mcps

Config shapes

User-wide (~/.grok/config.toml) vs project (.grok/config.toml — MCP is one of the things project config may hold):

[mcp_servers.demo]
command = "uvx"
args = ["some-mcp-package"]
enabled = true
startup_timeout_sec = 60   # cold npx/uvx often needs longer

HTTP/remote servers use a url + optional headers instead of command. OAuth-backed servers may store tokens under Grok’s credential files—treat those like passwords.

Compatibility

Grok can also pick up Claude/Cursor-style MCP configs for compatibility. Prefer one clear source of truth so you know what’s connected.

Tool names

MCP tools are often namespaced as <server>__<tool> in logs. You rarely type that—if a call fails, the error text naming the tool is useful for debugging with /mcps or doctor.

Trust

An MCP server can be as powerful as the APIs it holds. Only add servers you trust. Keep secrets in env vars, not chat.

Lab

  1. Open Grok and run /mcps. Note what is already connected (maybe nothing).
  2. Without installing anything risky, ask: “List MCP tools currently available to you.”
  3. Write one sentence: which real app you’d connect next (GitHub, Blender, tracker) and why.
Done when

You can explain MCP as “USB for tools,” know where config lives, and know /mcps is the TUI control panel.

Quick check

1. MCP mainly…
2. Before adding MCP servers…