---
title: "How to Connect Gomry to Claude"
meta_description: "Add Gomry to Claude as a custom connector, sign in with your Gomry account, and start asking about events, attendees, payments, and contacts."
canonical: "https://business.gomry.com/blog/how-to-connect-gomry-to-claude/"
comparison_date: "2026-09-14"
primary_keyword: "connect Gomry to Claude"
schema_type: "Article"
sources: ["https://docs.gomry.com/mcp/setup","https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp"]
internal_links: ["/blog/how-to-connect-gomry-to-chatgpt/","/blog/ai-event-management-software/","/blog/event-ticketing-api-webhooks/"]
cta_label: "Open MCP setup"
cta_url: "https://docs.gomry.com/mcp/setup"
---

# How to Connect Gomry to Claude

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](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp), checked on 14 September 2026, lists Free, Pro, Max, Team and Enterprise. Free accounts are limited to one custom connector.
- On Team and Enterprise, an Owner or Primary Owner adds the connector once for the organization. Members then connect their own accounts.

## 1. Add the connector

The Gomry MCP address is:

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

For an individual account:

1. In Claude, open **Customize → Connectors**.
2. Select **+**, then **Add custom connector**.
3. Name it `Gomry` and paste the address above.
4. Select **Add**.
5. Claude sends you to a Gomry page titled **Connect to Gomry**. It lists what the connector can do and the account you are signed in with. Select **Authorize**. You land back in Claude with the connector marked as connected.

That sign-in is OAuth. Gomry issues Claude its own credential, scoped to you and your organization. You do not need to fill in Client ID or Client Secret under Advanced settings.

For Team and Enterprise, the Owner goes to **Organization settings → Connectors**, selects **Add**, hovers **Custom** and picks **Web**, then pastes the same address. Members then open **Customize → Connectors**, find Gomry, and select **Connect** to sign in with their own Gomry 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 behaviour 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. If you cannot open the attendee list in the dashboard, Claude does not get an attendee tool. Everything is scoped to one organization on the server side, and the connector never raises anyone's 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.** On Team and Enterprise the Owner 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](/blog/ai-event-management-software/).