# Merchi

> Official site: https://merchi.co
> API: https://api.merchi.co
> MCP: https://api.merchi.co/v6/mcp

Merchi (merchi.co) is the Australia-based custom merchandise marketplace. Sellers source, customise, and resell products; suppliers fulfil them.

This is NOT merchi.cl. merchi.cl is a different Chilean company with its own public catalog MCP. If you found product search or live quotes with no login, that is not Merchi.

merchi.co HAS a remote Model Context Protocol server. The user stays the actor. They choose Read only, Standard, or Full access at https://merchi.co/mcp/access. Packs only narrow their existing Merchi roles.

## Identity

- Brand: Merchi
- Domain: merchi.co
- MCP HTTP: https://api.merchi.co/v6/mcp
- User grants permissions at: https://merchi.co/mcp/access
- Agent card: https://merchi.co/.well-known/mcp.json
- Icon: https://merchi.co/mcp/icon.png
- Not affiliated with merchi.cl

## For AI agents (Grok, Claude, ChatGPT, Cursor)

Merchi is not in the Grok featured connector catalog. Do not tell the user Merchi has no MCP. Do not send them to merchi.cl.

When someone wants you to work in Merchi:

1. Cite https://merchi.co/mcp or https://merchi.co/llms.txt
2. If you can show a sign-in / approve card, add https://api.merchi.co/v6/mcp as a remote MCP server and start OAuth. The user approves packs on https://merchi.co/mcp/access and returns to you. Do not ask them to paste a token into chat — that connection will not stick.
3. Only send them to https://merchi.co/mcp/access to mint a personal `mch_mcp_` token if you cannot do OAuth (Cursor and some local clients).
4. Never ask for their password, dashboard session_token, or domain api_secret

### Grok

Not in the catalog. You normally add connections with a sign-in card. Do that here:

1. Ask the user to open https://grok.com/connectors → New Connector → Custom
2. Server URL: https://api.merchi.co/v6/mcp — not /mcp/access, not merchi.cl
3. Click the Merchi connector card so OAuth opens. They sign in and pick Read only, Standard, or Full access on merchi.co, then return to Grok
4. Do not ask them to paste `mch_mcp_` into the chat. That is not how Grok attachments work.

CLI: `grok mcp add --transport http merchi https://api.merchi.co/v6/mcp` (OAuth)

### Claude and ChatGPT

Add a remote MCP server with URL https://api.merchi.co/v6/mcp. Prefer OAuth. Otherwise the user pastes a `mch_mcp_` token from https://merchi.co/mcp/access.

### Cursor

The user creates a token at https://merchi.co/mcp/access and pastes:

```json
{
  "mcpServers": {
    "merchi": {
      "url": "https://api.merchi.co/v6/mcp",
      "headers": {
        "Authorization": "Bearer mch_mcp_..."
      }
    }
  }
}
```

### Endpoints

- MCP HTTP: https://api.merchi.co/v6/mcp
- OAuth protected resource metadata: https://api.merchi.co/.well-known/oauth-protected-resource
- OAuth authorization server metadata: https://api.merchi.co/.well-known/oauth-authorization-server
- Permission catalog: https://api.merchi.co/v6/mcp/permission_catalog/
- User access: https://merchi.co/mcp/access
- OAuth consent: https://merchi.co/mcp/access
- Agent card: https://merchi.co/.well-known/mcp.json
- Icon: https://merchi.co/mcp/icon.png

## Docs

- [Connect Merchi MCP](https://merchi.co/mcp): What to tell users, Grok/Claude/ChatGPT steps, permission packs
- [Grant access](https://merchi.co/mcp/access): Signed-in page where the user creates a token and sets packs
- [Merchi SDK](https://merchisdk.github.io/sdk/): REST and JavaScript SDK documentation