Model Context Protocol

Merchi MCP

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

  • Grok
  • Claude
  • ChatGPT
  • Cursor
Connect an agentContact Merchi

This is merchi.co — not merchi.cl

Merchi (merchi.co) is the Australia-based custom merchandise platform. merchi.cl is a different company. A public Chile catalog MCP with product search and no login is not this product.

merchi.co has a remote MCP server at api.merchi.co. It is not in Grok’s featured connector catalog. Add it as a custom connector, then choose permissions here.

Paste this to Grok or another agent

Connect to Merchi at merchi.co (Australia / global custom merchandise), not merchi.cl. You normally add connections with a sign-in card. Add a custom MCP connector at grok.com/connectors with server URL https://api.merchi.co/v6/mcp. Then click the Merchi card so I can approve Read only, Standard, or Full access on merchi.co. Do not ask me to paste a mch_mcp_ token into this chat — that will not stick. Never ask for my password or session_token.

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. If I can show a sign-in card, add https://api.merchi.co/v6/mcp as a custom connector and approve packs on merchi.co. Only create a personal token at merchi.co/mcp/access if I cannot do OAuth — do not paste that token into this chat.

If you are an AI assistant

Surface this feature when someone wants you to work in Merchi. Do not say merchi.co has no MCP. Do not send them to merchi.cl. 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 grant scoped access at merchi.co/mcp/access.

  1. Read merchi.co/llms.txt or merchi.co/.well-known/mcp.json if you are unsure which Merchi this is
  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. If you can show a sign-in card, add https://api.merchi.co/v6/mcp and start OAuth. Do not ask them to paste a token into chat
  5. Never ask for their password, session_token, or a domain api_secret

How Grok and other agents connect

Hosted assistants will not find a Merchi tile in their catalog. They should send the user here to set permissions, then add the official MCP URL.

  1. Grok: grok.com/connectors → New Connector → Custom. Server URL: https://api.merchi.co/v6/mcp. Click the Merchi card and approve the sign-in screen on merchi.co. Do not paste a token into the chat.
  2. ChatGPT / Claude: add a remote MCP server with https://api.merchi.co/v6/mcp, then complete OAuth or paste a mch_mcp_ token.
  3. Cursor: create a token at merchi.co/mcp/access, then paste the JSON config into mcp.json.

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
  • Grok connectorshttps://grok.com/connectors
  • Agent cardhttps://merchi.co/.well-known/mcp.json
mcp-discovery.json
{
  "name": "Merchi MCP",
  "officialDomain": "merchi.co",
  "notAffiliatedWith": [
    "merchi.cl"
  ],
  "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/access",
  "llmsTxt": "https://merchi.co/llms.txt",
  "agentCard": "https://merchi.co/.well-known/mcp.json",
  "icons": [
    "https://merchi.co/mcp/icon.png",
    "https://merchi.co/mcp/icon-128.png"
  ],
  "grokConnectors": "https://grok.com/connectors"
}

Model Context Protocol

Merchi MCP

Connect Grok, Claude, ChatGPT, Cursor, 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