MCP configuration

Connect Grip to your browser, then add it to your editor or CLI — Cursor, VS Code, Claude Code, Gemini CLI, OpenCode, and more.

How it works

The @grip/cli daemon connects to any modern browser (Chrome, Edge, Brave) and safely exposes its internal state over the standard Model Context Protocol (MCP).

Setup requires two simple steps: Install the CLI on your system, and then paste the configuration block into your AI IDE. Your AI client will automatically manage the daemon lifecycle.

Installation

Install the CLI globally on your system to make the grip command available:

curl -fsSL https://grip.theshoaib.me/install | bash

Server config

This is the base configuration payload required by most MCP clients:

{
  "mcpServers": {
  "grip": {
    "command": "grip-cli",
    "args": ["mcp"],
    "env": {
      "GRIP_CHROME_PORT": "9222",
      "GRIP_LOG_LEVEL": "info"
    }
  }
  }
}

Client Setup Guides

Select your specific AI tool below to get the exact configuration snippet and file path required for integration.

Cursor

Config: .cursor/mcp.json (project) · ~/.cursor/mcp.json (user)

Root key: mcpServers

Supports ${workspaceFolder} in command paths.

Official MCP docs →

{
  "mcpServers": {
    "grip": {
      "command": "grip-cli",
      "args": ["mcp"],
      "env": {
        "GRIP_CHROME_PORT": "9222",
        "GRIP_LOG_LEVEL": "info"
      }
    }
  }
}

Troubleshooting

Connection refused

Port 9222 may be in use, or your browser was not started with the remote debugging flag enabled. Ensure you have completely closed Chrome and restarted it with --remote-debugging-port=9222.

Server not loading

Ensure you are using the correct root JSON key for your specific editor. For example, VS Code uses servers, Zed uses context_servers, and OpenCode uses mcp. Double check the client tab above.