Skip to main content
Orgo MCP connects AI assistants to your organization’s data using the Model Context Protocol (MCP), an open standard that lets tools like Claude securely talk to other apps. Once connected, you ask questions in plain language and the assistant looks up the answers in Orgo for you. AI assistant chat using Orgo MCP to check chapter renewal rates and send reminders to chapter leaders

​
What you can do

Most people use Orgo MCP for data analysis and light administrative actions:
  • Ask questions about your data: “How many members joined in June?”, “Which events this year had the most attendees?”, “Show unpaid membership fees by chapter.”
  • Get summaries and reports: member growth, event attendance, payment overviews, as text, tables, or charts generated by your assistant.
  • Take light actions: draft a newsletter, create an event, add a contact note. Review what the assistant proposes before it is saved.
Under the hood, the assistant has access to the full Orgo REST API (700+ operations across members, events, payments, newsletters, votes, and more), so anything the API can do, your assistant can do too.
The assistant acts with your permissions: it can only see and change what your own account can. Still, always review the actions it proposes before confirming them.
The hosted server is the easiest way to connect: nothing to install, always up to date:
Add this URL to your AI tool and sign in with the user on your Orgo workspace when prompted. Your organization is detected automatically from the account you log in with.

​
Your organization’s own address

Inside Orgo, under Website → Build by asking, administrators see an address specific to their organization, https://<your-org>.mcp.orgo.space/mcp, ready to copy. It is the same server and the same sign-in: use whichever of the two you have at hand. Organizations on their own domain get the shared address above.
  1. Go to Settings → Connectors → Add custom connector (on claude.ai or in the Claude Desktop app)
  2. Enter the URL https://mcp.orgo.space/mcp and click Add
  3. Sign in with your Orgo workspace account when prompted

​
Local server (developers)

For server-to-server automation, custom deployments, or local development, run the MCP server yourself from npm:
Example configuration using an API token (see API Access to create one):
The local server also supports JWT and OAuth token authentication and stdio, HTTP, and SSE transports. Full setup, configuration, and tool reference are in the repository README: github.com/Orgo-space/orgo-mcp.
An API token carries the access level of the administrator who created it, so keep it out of shared configurations. If the assistant only needs part of your data, create a restricted token: the scope you grant is exactly what the assistant can reach. See API Access.

​
Technical capabilities

​
Troubleshooting

Your AI tool could not reach the address you entered, so it never got as far as the Orgo login. Check the address for typos (it ends in /mcp), then remove the connector and add it again. If the organization-specific address keeps failing, use https://mcp.orgo.space/mcp: it is equivalent.
Sign-in opens in a browser window that pop-up blockers sometimes hide. Look for a blocked pop-up notice in the address bar, allow it, and retry. In Claude Code, run /mcp and pick the Orgo server to start the sign-in by hand.
The assistant works inside the organization of the account you signed in with. If you belong to several, sign out of the connector and sign in again with the account for the organization you want.
It has exactly your permissions. Anything your own account cannot see or change in Orgo, the assistant cannot either.