Connect your agent over MCP

Use this when

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 instead of OAuth. Create it in Console → Settings → API 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

1. 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.
2. Connect and complete Meguro’s browser sign-in and consent. In a conversation, open + → Connectors and enable Meguro.

Official Claude connector instructions.

Claude Code

1. Run claude mcp add --transport http meguro https://mcp.meguro.io/mcp.
2. Open Claude Code, run /mcp, select Meguro and complete browser authentication. Confirm it is connected before asking it to act.

Official Claude Code instructions.

Cursor

1. Select Add Meguro to Cursor, then review and accept Cursor’s server-install prompt. The link configures the same hosted endpoint shown above.
2. Complete browser authentication when prompted and enable the server for your agent.

Official Cursor install-link instructions.

ChatGPT web

1. Open Settings → Security and login and enable Developer mode. Availability depends on your account and workspace policy.
2. 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.
3. Start a new conversation and add the MCP connection from the tools menu.

Official ChatGPT connection instructions.

Codex and the ChatGPT desktop app

1. For the CLI, run codex mcp add meguro --url https://mcp.meguro.io/mcp, then codex mcp login meguro and complete browser consent.
2. 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.

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.

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. 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.