MCP server
Let AI assistants such as Claude, ChatGPT, Cursor and VS Code read and act on your Agoo data, within each person's permissions.
This is designed and scheduled but not built yet. We document it now so you can plan your integration.
The Agoo MCP server connects AI assistants to your organisation. Once it is connected, you can ask an assistant who is on site, find a visit, invite a guest or check attendance in plain language, and the assistant calls Agoo for you.
It speaks the Model Context Protocol (MCP), the open standard that assistants use to call outside tools. Any assistant that supports remote MCP servers can use it.
What people ask
| Who | Asks | Tool the assistant uses |
|---|---|---|
| Abena Asante, receptionist | "Who are we expecting at Ridge HQ this afternoon?" | search_visits |
| Kwame Mensah, host | "Invite Ama Owusu from Coastline Consult for 10:30 tomorrow and send her pass." | invite_visitor |
| Kofi Boateng, security lead | "Who is still missing from the Tema Branch roll call?" | roll_call_status |
| Esi Darko, admin | "How many people were late at the Kumasi Office last week?" | attendance_summary |
| Esi Darko, admin | "Who changed the kiosk settings at the Lobby on Monday?" | search_audit_log |
| Akwaaba Clinic's front desk | "Find a free consultation slot on Thursday and book Ama Owusu in." | find_available_slots, create_booking |
The full list, with inputs and outputs, is in the tools reference.
Example conversations
These show the shape of a conversation. The exact wording depends on the assistant you use.
Who is on site
Kofi: Who is on site at Ridge HQ right now?
Assistant (calls
who_is_on_sitewithsite_idfor Ridge HQ): There are 9 visitors checked in at Ridge HQ. Six are meetings, two are contractors from the lift maintenance company, and one is an interview candidate waiting for Kwame Mensah in Treasury. The earliest arrival checked in at 08:12 through the Main gate.Kofi: Which of them have been here more than four hours?
Assistant: The two contractors, both checked in at 08:12.
Inviting a guest
Kwame: Invite Ama Owusu from Coastline Consult to see me tomorrow at 10:30 at Ridge HQ. Her number is 024 123 4567.
Assistant (prepares
invite_visitor, with Kwame as the host): I'll create an expected visit for Ama Owusu (Coastline Consult) with you as host at Ridge HQ, tomorrow 14 October at 10:30, and send her pass to +233 24 123 4567. Shall I go ahead?Your assistant shows a confirmation with the exact details before anything is created.
Kwame: Yes.
Assistant: Done. Ama's visit is expected at 10:30 and her pass has been sent by SMS.
A roll call during a drill
Kofi: Is the Tema Branch roll call finished?
Assistant (calls
roll_call_status): Not yet. 41 of 44 people are accounted for. Still missing: one visitor last seen at the Main gate at 11:02, and two employees from Operations who clocked in this morning.
How permissions work
The assistant acts as the person who connected it, never as an administrator.
- Sign-in with OAuth. When you connect, you sign in to Agoo and approve the scopes the assistant asks for, such as
visits:readorbookings:write. Assistants identify themselves with a Client ID Metadata Document, or register themselves automatically if they don't support one, so nobody has to set them up by hand. See connect an assistant. - Your role and sites still apply. A receptionist who can only see Ridge HQ gets answers about Ridge HQ only, even if they ask about Kumasi.
- Admins approve the app. An admin approves each assistant app for the organisation once, and can revoke it at any time, which disconnects everyone using it.
- Tools follow scopes. The assistant only sees tools whose scope it was granted. Without
visits:write, it can't invite anyone. - Writes are confirmed. Tools that change data ask you to confirm first. Read tools are marked read-only so assistants can run them without interrupting you.
- Everything is audited. Each tool call is recorded in your organisation's audit trail with your name and the app that made it.
Details are in security and permissions.
Remote or local
There are two ways to run the server. Most people should use the remote one.
| Remote server | Local server | |
|---|---|---|
| Address | https://mcp.agoo.ardent.africa/mcp | Runs on your computer: npx -y @ardent-africa/agoo-mcp |
| Transport | Streamable HTTP | stdio |
| Signs in with | OAuth 2.1, as you | An API key in AGOO_API_KEY, as the key |
| Who it acts as | The person who connected it, with their role and sites | The key, with the key's scopes and access to the whole organisation |
| Best for | Everyday use in Claude, ChatGPT, Cursor and VS Code | Development, test mode, automation and tightly scoped keys |
| Plans (live mode) | Pro and Enterprise | Pro and Enterprise. Test keys work on every plan. |
| Set up | Connect an assistant | Run the local server |
MCP or Ask Agoo?
Agoo also has its own assistant, Ask Agoo, inside the console. It answers questions about your visitor and attendance data with no setup, uses your organisation's AI credits, and shows the working behind each answer.
Use the MCP server when you want Agoo alongside your other tools in an assistant you already use, for example to combine today's visitors with your calendar or your CRM in one conversation. MCP calls don't use AI credits; the assistant's own provider handles the AI side.