Catalyte
AI surfaces·advanced·6 min

MCP server

Connect Claude, ChatGPT, or any MCP client with OAuth 2.1 + DCR.

Catalyte runs two Model Context Protocol servers. The workspace server lets an AI client manage your catalog after the user signs in. The directory server is anonymous and read-only.

Endpoint

https://catalyte.dev/api/public/v1/mcp

Streamable HTTP transport (SSE). Authentication is either an API key bearer token, or an OAuth 2.1 access token.

Connect from Claude

  1. Open Claude → Settings → Connectors → Add custom connector.
  2. Paste the endpoint URL above and submit.
  3. Claude discovers the OAuth metadata, registers itself via DCR, and opens our consent screen.
  4. Approve the workspace. Claude stores the access and refresh tokens.

OAuth 2.1 + Dynamic Client Registration

Catalyte implements RFC 7591 (DCR), RFC 8414 (server metadata), RFC 9728 (protected resource metadata), and PKCE S256. Any compliant client works — no manual app setup required.

Connect from ChatGPT

ChatGPT's MCP support is rolling out. Until then, ChatGPT consumes Catalyte via the ACP SFTP feed.

Tools exposed

  • list_products — paginated read with optional query.
  • get_product — by SKU or id.
  • create_product — upsert by SKU.
  • update_product — partial patch.
  • delete_product — soft delete.
  • list_channels — enabled channels and their feed URLs.

Every tool call is recorded in Logs with the connected app, the user, and the diff.

Discovery endpoints

GET /.well-known/oauth-authorization-server
GET /.well-known/oauth-protected-resource
POST /api/public/v1/oauth/register
GET  /api/public/v1/oauth/authorize
POST /api/public/v1/oauth/token
POST /api/public/v1/oauth/revoke

Revoking access

Open API keys → Connected apps. Click Revoke. The access token and refresh token are deleted; the next tool call from that client returns 401 invalid_token with a WWW-Authenticate header that tells the client to reauthorize.

PreviousSFTP deliveryNext Public AI directory