# Connect your agent over MCP

Connect your own agent to Meguro’s hosted MCP server, approve access, and choose a practice scenario.

## Use this when

Use this when your agent speaks MCP. Meguro runs one hosted server; there is no Meguro package to install or local Meguro STDIO server to start.

## Before you start

Use this hosted endpoint, including `/mcp`: `https://mcp.meguro.io/mcp`.

Have a Meguro account, or create one during browser sign-in. Your first run on your own practice store costs nothing, and continuing it through its remaining planned Store days is also free. The automatic sample run does not count against your monthly runs. After your first run ends, starting a new run uses one monthly run.

### Browser consent and permissions
Sign in and approve only the requested access. Every browser approval creates a fresh grant; reconnecting does not replace or revoke older grants. The consent screen names the permissions it requests:

- View your practice stores

- Create and delete practice stores

- Read practice runs and receipts

- Start, advance, finish, and clean up practice runs

- Read store connection tokens

### Workspace API key alternative
Clients that support authorization headers can use a [workspace API key](/help/definitions#definition-workspace-api-key) instead of OAuth. Create it in [Console → Settings → API keys](https://app.meguro.io/#settings?section=keys) and configure `Authorization: Bearer <workspace API key>` in the client’s protected credential or header settings. The key remains bound to its workspace. Do not use a per-store Admin token, paste browser tokens or cookies, or put a key in a launch command, receipt or support message.

## Steps

### Claude.ai connectors

- In Claude.ai, open **Customize → Connectors**, select **+ → Add custom connector**, enter `https://mcp.meguro.io/mcp`, and select **Add**. On Team or Enterprise, an owner first adds the Web custom connector in **Organization settings → Connectors**; members then select **Connect**.

- Connect and complete Meguro’s browser sign-in and consent. In a conversation, open **+ → Connectors** and enable Meguro.

[Official Claude connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

### Claude Code

- Run `claude mcp add --transport http meguro https://mcp.meguro.io/mcp`.

- Open Claude Code, run `/mcp`, select Meguro and complete browser authentication. Confirm it is connected before asking it to act.

[Official Claude Code instructions](https://code.claude.com/docs/en/mcp).

### Cursor

- Select [Add Meguro to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=meguro&config=eyJtZWd1cm8iOnsidXJsIjoiaHR0cHM6Ly9tY3AubWVndXJvLmlvL21jcCJ9fQ%3D%3D), then review and accept Cursor’s server-install prompt. The link configures the same hosted endpoint shown above.

- Complete browser authentication when prompted and enable the server for your agent.

[Official Cursor install-link instructions](https://prod.cursor.com/docs/mcp/install-links).

### ChatGPT web

- Open **Settings → Security and login** and enable **Developer mode**. Availability depends on your account and workspace policy.

- Open **Plugins**, select **+**, enter the name **Meguro** and a description, and enter `https://mcp.meguro.io/mcp` under **Connection** as a public MCP server URL. Create the connection and complete browser consent.

- Start a new conversation and add the MCP connection from the tools menu.

[Official ChatGPT connection instructions](https://developers.openai.com/plugins/deploy/connect-chatgpt).

### Codex and the ChatGPT desktop app

- For the CLI, run `codex mcp add meguro --url https://mcp.meguro.io/mcp`, then `codex mcp login meguro` and complete browser consent.

- Alternatively, in the desktop app open **Settings → MCP servers → Add server**, name it **Meguro**, select **Streamable HTTP** and enter `https://mcp.meguro.io/mcp`. Save, select **Restart**, then **Authenticate**. The desktop app, CLI and IDE extension share the host’s MCP configuration.

[Official Codex and desktop instructions](https://learn.chatgpt.com/docs/extend/mcp?surface=cli).

### Compatibility bridge
If your client accepts only a command, configure `npx -y mcp-remote https://mcp.meguro.io/mcp` as its MCP launch command and complete browser consent. This is a third-party bridge to the hosted server, not a local Meguro server. Prefer the direct URL when your client supports it. [Bridge instructions](https://github.com/punkpeye/mcp-remote).

## Success looks like

The client lists Meguro’s tools. Ask it: “Choose a practice scenario, read its brief, and do what the brief asks. Bring me back the receipt link.” It should read the server-owned scenario and run plan before starting.

## If it fails

If authentication fails, confirm the endpoint includes `/mcp` and reconnect through your client’s authentication control. Reauthorization creates a fresh grant; revoke any older grants you no longer want. A client that lacks remote HTTP support needs the compatibility bridge above.

## Next action

Review and revoke access at [Console → Settings → Connection → MCP authorizations](https://app.meguro.io/#settings?section=connection). Revocation stops refresh immediately; an issued access token can remain valid for up to 15 minutes. Remove the connection in your client separately to clear its local configuration.