MCP server: connect AI assistants to your organization

Connect from any assistant that supports MCP:

• Claude (claude.ai and Claude Code)
• ChatGPT and other MCP-compatible assistants
• Custom agents and internal tools your team builds

Instead of a fixed list of pre-wired commands, the assistant explores the API itself: it lists the available operations, reads how each one works, and then calls the one it needs. New Orgo features become available to assistants without reconfiguring anything.

The server ships its own docs as MCP resources, so the assistant can read how authentication, pagination, and filtering work before making a single call.

A single connection covers:

• People — members, contacts, families, companies
• Events — tickets, attendance, speakers, vouchers
• Payments — invoices, products, billing
• Contracts and e-signatures
• Communications — newsletters, discussions, notifications
• Governance and learning — voting, org charts, courses, badges

Assistants are not limited to lookups. With a write-scoped token, an assistant can create and update records — register an attendee, update a member's details, or draft a newsletter — using the same validated API the Orgo apps use.

Each token sets None, Read, or Write independently for four areas:

• Members — records, groups, courses, contracts, badges, votes
• Events — events, attendance, tickets, speakers
• Financial — invoices, payments, products, billing
• Communications — newsletters, discussions, posts

A token for an event-planning assistant can write Events data while seeing nothing financial at all.

A full-access read-only token lets an assistant answer questions across the whole platform while rejecting every modification attempt — the safest starting point for most organizations.

Every endpoint in the platform is classified into a permission category, and anything unclassified is denied automatically. Sensitive areas — authentication flows, billing configuration, webhooks administration, data imports — are permanently off-limits to scoped tokens, regardless of what they were granted.

Only tenant admins can create tokens, and each token is:

• Shown once at creation, never retrievable again
• Optionally set to expire on a date you choose
• Revocable instantly, cutting off any integration that used it

Each token records when it was last used, and every change to a token's permissions is written to an audit log, so you can always answer who could access what, and when.

Every call is scoped to your organization's own workspace. Cross-organization reads are blocked at the persistence layer, so even a misdirected query cannot leak another organization's data.

Every resource follows the same conventions — pagination, filtering, ordering, validation — so once an assistant learns one endpoint, it knows the shape of all of them.

The same developer platform also offers:

• Webhooks for pushing events (payments, registrations, contract signatures) to your own systems
• OAuth 2.0 for building "Log in with Orgo" into third-party apps
• Plain REST access for scripts and scheduled jobs