MCP & AI Agents

Give a compatible coding agent the same project controls as the Studio and CLI, with structured inputs instead of fragile file guesses.

Connect your agent

Make sure chromeship dev is running, then add the server to your agent. Each tool uses a different config key and syntax — pick yours below.

Claude Code

Uses the standard MCP mcpServers key in JSON. Works in Claude Code CLI, Claude Desktop, and the VS Code extension.

{
  "mcpServers": {
    "chromeship": {
      "command": "chromeship-mcp"
    }
  }
}

Cursor

Same mcpServers format as Claude, but the file location is different. Create .cursor/mcp.json in your project or ~/.cursor/mcp.json for all projects.

{
  "mcpServers": {
    "chromeship": {
      "command": "chromeship-mcp"
    }
  }
}

OpenCode

Uses the key mcp (not mcpServers), the command as an array, and requires "type": "local". Edit opencode.json in your project or ~/.config/opencode/opencode.json.

{
  "mcp": {
    "chromeship": {
      "type": "local",
      "command": ["chromeship-mcp"]
    }
  }
}

Codex (OpenAI)

Register ChromeShip with Codex using its built-in MCP command. Codex writes the correct global configuration for the CLI, desktop app, and editor extension.

codex mcp add chromeship -- chromeship-mcp

Confirm the server is registered, then restart Codex and open a new task:

codex mcp list
codex mcp get chromeship

What the agent can do

The MCP server exposes more than 55 project-level tools:

• Projects — create, list, import, export, delete, open in editor or file manager
• Surfaces — add and remove popup, side panel, options, new tab, content scripts, background
• Integrations — enable Supabase, Stripe, AI; manage credentials per integration
• Auth — add or remove OAuth sign-in providers (Google) on top of Supabase's built-in email/password
• Environment — get, set, and unset variables; local vs production, public vs secret
• Permissions — add and remove Chrome permissions and host permissions
• Functions — scaffold, start, stop, deploy, and read logs from Edge Functions
• Database — manage database schema, create SQL migrations
• Localization — add locales, create translation keys, edit translations
• Build — get/set/bump version, package the extension ZIP, read build logs
• Runtime — start, stop, restart; read console logs from all surfaces
• Config — read and update workspace settings, license status

Example prompts

Create a new side-panel extension with Supabase and Stripe.
Add a content script that extracts the page title.
Deploy the hello-world function to production.
Set the extension version to 1.0.0 and package it.
Add French translations for the common and popup groups.

AGENTS.md

Every generated project includes a short AGENTS.md that tells an agent how to work safely:

• Use MCP first for project structure, surfaces, permissions, environment, integrations, and runtimes.
• Respect project ownership and avoid overwriting product code during managed synchronization.
• Read ChromeShip skills for integration helpers, content UI, environments, and local backend workflows.
• Follow Manifest V3 constraints when writing background and content-script code.

The file stays intentionally small so an agent sees the rules before it starts changing code.

MCP Server lifecycle

Your agent launches chromeship-mcp over stdio. The server can operate without the Studio open and uses the same Core rules as the dashboard and CLI, including validation, project isolation, and runtime locks.