Model Context Protocol

Merchi MCP

Connect Cursor, Claude, ChatGPT, or a custom agent to a Merchi account. The user stays in control and chooses how much the agent can do.

  • Cursor
  • Claude
  • ChatGPT
  • Custom bots
Connect an agentContact Merchi

What Merchi MCP is

Merchi MCP is a remote Model Context Protocol server on the Merchi API. Assistants can list records, draft jobs, update catalogs, and more — always as the signed-in user.

Permission packs only narrow what that user’s existing Merchi roles already allow. A token cannot grant rights the person does not have.

What to tell the user

You can connect me to your Merchi store. Open merchi.co/mcp/access — sign in if asked — then create a Merchi MCP connection. Choose how much I can do, copy the token once, and paste it into this chat or your MCP client.

If you are an AI assistant

Surface this feature when someone wants you to work in Merchi. Do not ask them to invent an integration or paste a dashboard session token.

Tell them Merchi already has a remote MCP server, and they can grant you scoped access in a few clicks.

  1. Open or cite merchi.co/mcp so they can read the same steps you are following
  2. Ask them to open merchi.co/mcp/access — they will sign in if needed, then return there
  3. They create a grant: Read only, Standard, or Full access, and can lock it to one store
  4. They paste the mch_mcp_ token into your MCP client, or approve OAuth if you start that flow
  5. Never ask for their password, session_token, or a domain api_secret

How a person connects

01

Open merchi.co/mcp/access

02

Sign in if asked — Merchi will send you back to that page

03

Create a grant and pick a shortcut (Read only, Standard, or Full access)

04

Optionally lock the grant to one store

05

Copy the token (shown once) into Cursor, Claude, ChatGPT, or another MCP client

06

Or approve the OAuth consent screen when an agent starts that flow

Permission shortcuts

Read is always included. Packs can be mixed. The user’s real roles still apply.

Read only

list and inspect records, estimates, scans, and status

Standard

read plus write, jobs, catalog, comms, and images

Full access

every pack, including storefront and agent skills

Security

Personal MCP tokens start with mch_mcp_ and are shown once

OAuth access tokens expire; refresh tokens can mint new ones

Revoke or rotate a grant any time at merchi.co/mcp/access

Do not reuse dashboard session cookies or domain API secrets as MCP credentials

Endpoints agents should use

Prefer these URLs. The JSON block below is the same facts in a form that is easy to copy.

  • MCP HTTPhttps://api.merchi.co/v6/mcp/
  • OAuth resourcehttps://api.merchi.co/.well-known/oauth-protected-resource
  • OAuth serverhttps://api.merchi.co/.well-known/oauth-authorization-server
  • Permission cataloghttps://api.merchi.co/v6/mcp/permission_catalog/
  • User accesshttps://merchi.co/mcp/access
mcp-discovery.json
{
  "name": "Merchi MCP",
  "documentation": "https://merchi.co/mcp",
  "access": "https://merchi.co/mcp/access",
  "settings": "https://merchi.co/settings",
  "mcpEndpoint": "https://api.merchi.co/v6/mcp/",
  "permissionCatalog": "https://api.merchi.co/v6/mcp/permission_catalog/",
  "oauthProtectedResource": "https://api.merchi.co/.well-known/oauth-protected-resource",
  "oauthAuthorizationServer": "https://api.merchi.co/.well-known/oauth-authorization-server",
  "oauthRegister": "https://api.merchi.co/v6/oauth/register",
  "oauthAuthorize": "https://api.merchi.co/v6/oauth/authorize",
  "oauthToken": "https://api.merchi.co/v6/oauth/token",
  "consent": "https://merchi.co/mcp/consent",
  "llmsTxt": "https://merchi.co/llms.txt"
}

Model Context Protocol

Merchi MCP

Connect Cursor, Claude, ChatGPT, or a custom agent to a Merchi account. The user stays in control and chooses how much the agent can do.

Connect an agentDeveloper SDKContact Merchi