METAGROK
BUILD / list-mcp-servers-with-grok-cli

Build

List MCP servers with the Grok CLI

list-mcp-servers-with-grok-cli

See every MCP server Grok Build has loaded for this workspace — user config, project .grok/config.toml, and vendor compat files — before you debug a missing tool or toggle a remote. Official MCP Servers documents grok mcp list (and --json for machine-readable output), and the CLI Reference lists grok mcp <list|add|remove|doctor> as the management surface. Install the CLI from the Grok Build overview if it is not already on your PATH.

What you need

The Grok Build CLI signed in (grok login), a project directory that may define project-scoped servers, and optional MCP entries already saved under ~/.grok/config.toml, .grok/config.toml, or compat files such as .cursor/mcp.json. Neighboring jobs include Add MCP servers in Grok Build when a server is missing, Diagnose MCP servers with grok mcp doctor when a listed server fails to connect, and Inspect Grok Build config with grok inspect when you need origin and merge order for every loaded server. More Build jobs live on the Build hub.

List from the shell

  1. Change into the repo (or pass --cwd later) and confirm the CLI responds:
cd /path/to/your-project
grok version
  1. Print the human-readable server list for the configuration Grok will load here:
grok mcp list
  1. Prefer JSON when a script or CI step must assert that a named server is present:
grok mcp list --json
  1. Cross-check discovery with grok inspect (or grok inspect --json) so you see each server’s origin — user config.toml, project .grok/config.toml, Claude/Cursor compat files, and so on. Grok merges vendor MCP configs from ~/.claude.json, .cursor/mcp.json, and project .mcp.json below config.toml unless you disable a vendor under [compat.claude] / [compat.cursor].

List and toggle in the TUI

Inside an interactive grok session, open the MCP tab of the extensions modal with /mcps. Official docs map Space to toggle a server, r to refresh after config edits, i to authenticate OAuth remotes, and a / x to add or remove. After a project teammate lands a new .grok/config.toml block, refresh the list before you assume the tool namespace <server>__<tool> is available.

Pitfalls

Listing from the wrong working directory hides project-scoped servers that only exist under that tree’s .grok/config.toml. Expecting grok mcp list to prove connectivity is wrong — use grok mcp doctor when a name appears but tools never fire. Disabling Claude or Cursor compat after a list that showed a vendor-only server will make that name disappear on the next inspect without deleting your config.toml entries.