Connect an assistant
Add the Agoo MCP server to Claude, Claude Code, ChatGPT, Cursor, VS Code or any client that supports remote MCP servers.
This is designed and scheduled but not built yet. We document it now so you can plan your integration.
You connect an assistant to Agoo by giving it one address and signing in. There is no key to copy.
https://mcp.agoo.ardent.africa/mcpBefore you start
- Your organisation is on Pro or Enterprise. On other plans, try the local server with a test key instead.
- You have an Agoo account with access to the sites you want to ask about. The assistant gets your permissions, no more.
- An admin approves the app. The first time anyone in your organisation connects a particular assistant (for example, Claude), an admin approves it for the organisation. After that, everyone else just signs in.
These instructions will work once the server is live. Menu names in each client are as published by its maker at the time of writing and can change.
Add the server to your client
This works in Claude on the web (claude.ai) and in Claude Desktop.
Add a custom connector
Open Customize → Connectors, select +, then Add custom connector. Name it Agoo and paste the server URL https://mcp.agoo.ardent.africa/mcp. Leave Advanced settings empty: Agoo registers Claude automatically. Select Add.
On Claude Team and Enterprise plans, only an owner can add custom connectors. The owner adds it in Organization settings → Connectors → Add → Custom → Web, and members then connect from Customize → Connectors. On Claude's Free plan you can have one custom connector.
Connect and sign in
Select Connect. A browser window opens at Agoo. Sign in and approve access (see what you approve).
Turn it on in a conversation
In a chat, select + at the bottom left, then Connectors, and switch on Agoo. You can choose which Agoo tools Claude may use in the connector's settings.
What you approve
When your client opens the Agoo sign-in page, this is what happens:
Sign in
Sign in as you normally do, including single sign-on if your organisation uses it. If you belong to more than one organisation, choose the one this assistant should work with. A connection is always to one organisation.
Review the access requested
Agoo shows the app's name, the address it will send you back to, and the scopes it asks for in plain language, for example "See visits at the sites you can access" for visits:read and "Invite visitors and check them out" for visits:write. You can untick write scopes to keep the assistant read-only. Scopes your role doesn't allow are shown as unavailable and are never granted.
Approve, or ask an admin
If an admin has already approved the app for your organisation, select Allow and your client is connected.
If not, select Request approval. Your organisation's admins are notified. Once one of them approves the app, connect again from your client.
The scopes an assistant can ask for over MCP are organisation:read, sites:read, people:read, visits:read, visits:write, deliveries:read, bookings:read, bookings:write, attendance:read, rollcalls:read and audit:read. See which tool needs which scope in the tools reference.
For admins: approving an app
Admins see pending and approved apps in Console → Developers → Connected apps. For each app you can see its client ID (for most assistants, the web address of its metadata document), who first connected it, its redirect addresses and the scopes it may request.
- Approve to let people in your organisation connect it. You can approve it for read scopes only.
- Revoke to disconnect everyone using it immediately. Their access and refresh tokens stop working.
- Each person can also disconnect their own connections from Profile → Connected apps.
After you connect
- Access tokens last 1 hour and your client refreshes them on its own. Refresh tokens rotate each time they're used.
- If you lose access to a site or your role changes, the assistant's answers change straight away.
- If your organisation moves to a plan without MCP access, tool calls return a
plan_requirederror that your assistant will show you.
Troubleshooting
An admin hasn't approved this assistant for your organisation yet. Select Request approval, wait for an admin to approve it in Console → Developers → Connected apps, then connect again.
The tool's scope wasn't granted, or your role doesn't allow it. Disconnect and connect again, and leave the scope ticked. For example,
invite_visitor needs visits:write.
Live MCP access needs Pro or Enterprise. Ask an admin to check your plan, or use the local server with a test key to try it.
Each connection is to one organisation. Disconnect, connect again and choose the right organisation at sign-in. To use two organisations, add the
server twice under different names, such as agoo-volta and agoo-coastline.
MCP shares your organisation's API rate limit. The error says how many seconds to wait. If it happens often, an integration may be using most of the limit; see rate limits.
When you contact support, include the Agoo-Request-Id from the error if your client shows it.