Gomry runs a remote MCP server. Add it to Claude as a custom connector and Claude can use Gomry's documented tools for events, attendees, forms, applications, contacts and experiences, and read payment records. You ask in plain language. Claude calls the Gomry tool your role already allows.
You sign in with your Gomry account. No API key is involved.
What you need
- A Gomry account with access to the organization you want to work in.
- Claude on the web, Claude Desktop, or Cowork. Claude's connector documentation lists Free, Pro, Max, Team and Enterprise. Free accounts are limited to one custom connector.
- On Team, an Owner or Primary Owner adds the connector for the organization. Enterprise also allows a custom role with Manage access to Libraries. Members connect their own accounts.
1. Add the connector
The Gomry MCP address is:
`` https://www.gomry.com/api/mcp ``
For an individual account:
- In Claude, open Customize → Connectors.
- Select +, then Add custom connector.
- Name it
Gomry, enter the server address and select Continue. - Review the detected authentication settings, then select Continue.
- Choose Sign in now under Authentication, then Register automatically for the OAuth client. Gomry supports dynamic client registration; you do not need to supply a Client ID, Client Secret or extra request headers.
- Select Add and complete the Gomry sign-in and authorization when prompted. Review the account and requested access before authorizing.
Gomry uses OAuth sign-in rather than an organizer API key. Authorize the Gomry account whose events and contacts you want Claude to work with.
For Team and Enterprise, an authorized administrator starts under Organization settings → Connectors → Add → Custom → Web, then follows the same address, authentication and OAuth-client configuration steps. Members open Customize → Connectors, find Gomry and select Connect to sign in with their own account.
2. Turn it on in a chat
Open a new conversation. Select + next to the composer, open Connectors, and switch Gomry on. The connector stays configured; the toggle decides whether this conversation can use it.
Start with something that only reads:
- "List my upcoming events."
- "Who is checked in for Friday's event, and who is still pending?"
- "Total successful payments by event for last month."
- "Show the answers to the volunteer form, grouped by question."
Claude shows each Gomry tool it calls. Compare the organization name, event names, dates, and totals with your dashboard before you trust the rest.
3. Make one change on purpose
Once the reads look right, try one small update your role permits. Name the record and the new value: "Set the capacity of Sunset Sessions on 18 September to 220. Show me the event first."
Review Claude's approval request and the tool arguments before a change. Allow always permits a trusted tool to run without a fresh approval, so confirmation behavior depends on the permissions you choose. A tool that reads payments does not imply support for refunds.
What Claude can and cannot see
Access follows your Gomry role in each organization you belong to. If you cannot open an organization's attendee list in the dashboard, Claude cannot use an attendee tool there. Name the organization when your account belongs to more than one: each operation applies to the selected organization's records, and the connector never raises your permissions.
To stop access: switch the connector off in the conversation, or open it under Customize → Connectors and select Disconnect. Connecting again runs the same Gomry authorization.
The API keys under Organization Settings in Gomry are a different thing. They are for code you write against the Gomry API and do not work in Claude. The connector needs no key at all.
Troubleshooting
The address shows an error in the browser. Expected. The MCP endpoint answers JSON-RPC requests from Claude, not page visits. If you open it directly you see a message about missing authentication. Paste it into Claude instead.
Claude cannot reach the server. Check that you pasted the exact address and did not add a path. Claude connects from Anthropic's cloud, so the server must be public; Gomry's endpoint is.
Some tools are missing. Check the role of the account you signed in with. Tool visibility mirrors dashboard permissions.
Claude asks you to sign in again. Open Gomry under Customize → Connectors and select Connect. You go through the same Gomry authorization page and come back connected.
A team member does not see Gomry. An authorized administrator has to add it first under Organization settings → Connectors. Each member still selects Connect on their own account.
Confirm one named event in Claude against the dashboard. Before requesting changes, review the MCP task and permission guide.