Gomry MCP Server
The Gomry MCP server lets AI assistants like Claude, ChatGPT, Cursor, and Codex read and manage your organization’s data directly — events, attendees, forms, applications, payments, contacts, experiences, and more — without you copying anything by hand. It’s the same data the Public API exposes, but instead of writing HTTP calls, you give your AI client a single URL and it discovers the available tools on its own.Best for: analyzing form submissions, summarizing attendee lists, querying payments, exploring contacts, updating event data, and building one-off workflows where writing code would be overkill. Not for: programmatic integrations — use the Public API for those.
What you can ask
Once connected, your AI assistant can answer questions like:Form submissions
“What did people answer on form X? Group the responses by question.”
Attendee analysis
“Who’s checked in vs. still pending for next week’s event?”
Payment review
“Show me last month’s successful payments by event.”
Cross-resource
“Which contacts have submitted applications but never paid?”
How it differs from the API key
The two systems are independent — your API keys won’t authenticate MCP calls and an MCP connection won’t authenticate API calls.
Security model
- Every MCP connection is tied to one user. Calls are scoped server-side to the organizations that user belongs to; an MCP client can never read or modify any other organization’s data.
- Tool visibility mirrors your dashboard privileges. If you can’t see attendees in the dashboard, the
list_attendeestool isn’t even advertised to your client. - Connections are revocable from the client: disconnecting the Gomry connector revokes its refresh token, and the current access token expires within the hour.
- The endpoint is rate-limited at 120 requests per minute per user.
Next steps
Setup
Connect Claude, ChatGPT, or Cursor with OAuth in under two minutes.
Available tools
The full list of MCP tools and what they return.