Setup

The Gomry MCP server is a hosted remote MCP endpoint. There is nothing to install and no token to copy: you add one URL to your AI client, sign in to Gomry when it asks, and you’re done.

https://www.gomry.com/api/mcp

1. Add the connector

Add Gomry as a custom MCP server

In your AI client, add a new custom connector / MCP server and paste the URL above. Leave any bearer-token or custom-header fields empty. Client-specific steps are in the tabs below.

Authorize

The client opens a Gomry page in your browser. Sign in with your Gomry account if you aren’t already, then click Authorize.

Any signed-in Gomry user can connect. The assistant gets access to every organization you’re a member of, limited to what your role in each one allows.

Done

You’re redirected back to the client, which loads the tool list and shows Gomry in its tool picker.

2. Client-specific instructions

Claude
ChatGPT
Cursor
Codex and other CLIs
Other clients

Open Settings → Connectors.
Click Add custom connector.
Name it Gomry and paste the server URL:
https://www.gomry.com/api/mcp
Click Add, then Connect. Authorize in the Gomry page that opens.

Open Settings → Connectors (or Apps, depending on the version).
Click Create / Add custom connector.
Name it Gomry and paste the MCP server URL:
https://www.gomry.com/api/mcp
Leave authentication on OAuth and save. Authorize in the Gomry page that opens.

Add this entry to your ~/.cursor/mcp.json (create the file if it doesn’t exist):

{
  "mcpServers": {
    "gomry": {
      "url": "https://www.gomry.com/api/mcp"
    }
  }
}

Open Cursor’s MCP settings and click the login / authenticate action next to gomry to run the OAuth flow.

Add https://www.gomry.com/api/mcp as a streamable HTTP MCP server, leave the bearer-token and custom-header options empty, then run the client’s login / authenticate command for that server. It opens the Gomry authorization page in your browser and calls back to a local port on your machine.

Any client that supports remote MCP over streamable HTTP with OAuth works. Configure it with:

Setting	Value
Server URL	`https://www.gomry.com/api/mcp`
Transport	Streamable HTTP
Authentication	OAuth (leave tokens/headers empty)

The server publishes standard discovery documents, so clients find the authorization server on their own:

https://www.gomry.com/.well-known/oauth-protected-resource
https://www.gomry.com/.well-known/oauth-authorization-server

3. Verify it works

In your client, ask:

“List my events.”

The assistant should invoke the list_events tool and return your organization’s events. If you belong to more than one organization, it may ask which one you mean.

How authentication works

The server is an OAuth 2.1 authorization server (PKCE, dynamic client registration) in front of the MCP endpoint:

The client discovers the authorization server via /.well-known/oauth-protected-resource.
The client registers itself and sends you to the Gomry authorization page.
You sign in (Firebase auth, same as the dashboard) and click Authorize.
The client receives a short-lived access token (1 hour) and a refresh token (30 days, rotated on every use), and sends the access token as Authorization: Bearer … on each MCP call.

Nothing is shared with the client beyond access to the tools your privileges allow. If a client explicitly requests the openid / email scopes (some workspaces require it), Gomry also returns your account email and whether it’s verified — nothing else.

Disconnecting

Remove or disconnect the Gomry connector in your AI client. This revokes the refresh token on Gomry’s side, so the client can’t renew access; the current access token expires within the hour. You can reconnect at any time by running the authorization flow again.

Alternative: personal token URL

If your client can’t run OAuth, you can use a personal token instead:

In the Gomry dashboard, open Personal Settings (your account settings, not organization settings) → Connect to Claude.
Click Generate Server URL and copy the URL. It looks like https://www.gomry.com/api/mcp?token=… and is shown once.
Paste it as the server URL in your client. The token is accepted as ?token= or Authorization: Bearer ….

Treat the URL like a password: anyone holding it can act as you across every organization you belong to. You have at most one active token; Regenerate replaces it and Revoke (same section) disables it within five minutes.

Errors you might hit

Status	Body	Meaning
`401`	`Missing authentication.`	The client isn’t sending credentials. Re-run the connector’s login / authorize step.
`401`	`Invalid or expired access token`	The OAuth session expired and couldn’t be refreshed. Disconnect and reconnect the connector.
`401`	`Invalid or revoked MCP token`	Personal-token path: the token was revoked or regenerated. Generate a new URL.
`429`	`Rate limit exceeded.`	More than 120 requests/minute for this user. Slow down.
`-32001` (JSON-RPC)	`Tool not found: …`	The tool exists but your privileges don’t include it, OR the tool name is wrong. See Available tools.
OAuth	`redirect_uri does not match a registered redirect URI`	Seen with older CLI clients that pick a random local port. Remove the server from the client and add it again.

Getting Started

MCP Server

Agentic Commerce

Webhooks

Setup

Setup

1. Add the connector

2. Client-specific instructions

3. Verify it works

How authentication works

Disconnecting

Alternative: personal token URL

Errors you might hit

​Setup

​1. Add the connector

​2. Client-specific instructions

​3. Verify it works

​How authentication works

​Disconnecting

​Alternative: personal token URL

​Errors you might hit

Setup

1. Add the connector

2. Client-specific instructions

3. Verify it works

How authentication works

Disconnecting

Alternative: personal token URL

Errors you might hit