Skip to content

Connect your agent

Add the merchant MCP server to Claude, ChatGPT, Gemini CLI, Grok, Claude Code, Codex, Cursor or any other MCP client.

Updated

Your assistant works on your store as you, with only the stores and permissions you approve. You can disconnect it anytime from your Connections page.

The Merchant MCP URL is:

https://mcp.sherpo.io

The same URL with /mcp at the end works too.

In the merchant app, Connect to your agent in the account menu shows the same steps and the same URL, with a button to copy it.

Pick your AI

  1. Add a custom connector

    In Claude, on the web or desktop, open Customize, then Connectors, click + Add, then Add custom connector. Name it Sherpo, paste the Merchant MCP URL, https://mcp.sherpo.io, and click Continue.

  2. Choose how it signs in

    Keep the detected settings and click Continue. Under Authentication, choose Sign in now, and under OAuth client, choose Register automatically: Sherpo’s sign-in takes apps that register themselves, not Claude’s published identity.

  3. Approve access

    Click Add and approve access on the Sherpo page that opens, titled Connect Claude to Sherpo. Then ask for what you want.

  1. Add a custom MCP server

    In ChatGPT on the web, open Plugins, click + and choose Add custom MCP server. Name it Sherpo, paste the Merchant MCP URL, https://mcp.sherpo.io, under Connection and choose OAuth.

  2. Sign in

    Sign in with your Sherpo account and approve access. Review the warning, choose I understand and want to continue, then Create as a plugin.

  3. Install it and ask

    Find Sherpo in your plugins, or your workspace’s, and install it. Then start a new conversation, type @, pick Sherpo and ask for what you want.

  1. Add Sherpo to your settings

    Open the Gemini CLI settings file and add Sherpo under mcpServers. If the file already has an mcpServers block, add the sherpo entry inside it.

    In ~/.gemini/settings.json:

    {
      "mcpServers": {
        "sherpo": {
          "httpUrl": "https://mcp.sherpo.io"
        }
      }
    }
  2. Sign in

    Restart the Gemini CLI, run this command and approve access in your browser. Then ask for what you want.

    /mcp auth sherpo
  1. Add a custom connector

    On grok.com, open Connectors, click New connector, choose Custom and paste the Merchant MCP URL, https://mcp.sherpo.io.

  2. Approve access

    Sign in with your Sherpo account when Grok asks, and approve access. Then ask for what you want.

  1. Add Sherpo

    Run this in your terminal.

    claude mcp add --transport http sherpo https://mcp.sherpo.io
  2. Sign in

    Start Claude Code, run /mcp, pick sherpo and authenticate in your browser. Then ask for what you want.

  1. Add Sherpo

    Open the Codex config file and add an entry for Sherpo.

    In ~/.codex/config.toml:

    [mcp_servers.sherpo]
    url = "https://mcp.sherpo.io"
  2. Sign in

    Start Codex and approve access in your browser. If no sign-in opens, run codex mcp login sherpo in your terminal.

  1. Add Sherpo

    Open Cursor’s MCP config file and add Sherpo under mcpServers. If the file already has an mcpServers block, add the sherpo entry inside it.

    In ~/.cursor/mcp.json:

    {
      "mcpServers": {
        "sherpo": {
          "url": "https://mcp.sherpo.io"
        }
      }
    }
  2. Sign in

    In Cursor’s settings, open MCP, click Connect next to sherpo and approve access in your browser. Then ask for what you want.

Approving access opens Sherpo’s consent screen, where you pick the businesses, their stores and what the connection may do in each. Sign-in and consent explains each choice.

Any other MCP client

Any client that supports remote MCP servers with OAuth can connect. Point it at https://mcp.sherpo.io. What it needs:

  • Transport: Streamable HTTP. The server is stateless and answers with JSON: there is no session and no server stream, so every request is a POST.
  • Protocol: MCP 2026-07-28, and the earlier revisions 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 and 2024-10-07 over the 2025-era transport. A request whose params._meta carries no io.modelcontextprotocol/protocolVersion is served the 2025-era way. Such a request must send Accept: application/json, text/event-stream, or it answers 406.
  • Sign-in: OAuth 2.1 with the authorization code flow and PKCE (S256). The client registers itself with dynamic client registration, so there is nothing to set up in Sherpo first.
  • Batches: a JSON-RPC batch (an array of requests) is refused. Send one request at a time.
  • Tools only: the server offers tools, with no prompts or resources.

A client that reads the common mcpServers shape takes:

{
  "mcpServers": {
    "sherpo": {
      "url": "https://mcp.sherpo.io"
    }
  }
}

Sign-in and consent covers discovery, registration and tokens for client developers, and Calling tools covers the calls themselves.

Open the URL in a browser

A browser visiting the URL is sent to the server’s own help page. It lists every tool with its scope, the scope sets, and short guides on connecting, errors and paging.

Type to search…

↑↓ navigate↵ selectEsc close