Povio AI Access — MCP server
Open the app →Povio AI Access manages who at Povio has which AI tool seat (Claude, Cursor, Codex), plus the access requests, approvals, reviews, offboarding, costs and settings around them. Everything you can do in the web app, an AI agent can do through this MCP server. The signed-in person's app role (employee, approver or administrator) decides what is allowed, exactly as in the app.
If you are an AI agent reading this page: connect your MCP client to the endpoint below. Your client handles sign-in with OAuth; the user signs in with their Povio Google account in the browser. Then call whoami before anything else. It returns the user's roles and allowedTools, the tools this user may call.
https://prj-zw4fcvouv9mh.robodev.povio.dev/mcp
Transport: Streamable HTTP (JSON-RPC over POST). Authentication: OAuth 2.1, discovered automatically through /.well-known/oauth-protected-resource/mcp. You don't need an API key.
Connect
Claude Code
claude mcp add --transport http povio-ai-access https://prj-zw4fcvouv9mh.robodev.povio.dev/mcp
Then run /mcp inside Claude Code, select povio-ai-access and choose Authenticate.
Codex (CLI or ChatGPT desktop)
codex mcp add povio-ai-access --url https://prj-zw4fcvouv9mh.robodev.povio.dev/mcp
Complete the browser sign-in. If no sign-in opens, run codex mcp login povio-ai-access.
Claude.ai and Claude Desktop
Settings → Connectors → Add custom connector. Name: Povio AI Access. URL: the endpoint above. Then connect and sign in with your Povio account.
Cursor
Cursor Settings → Tools & MCP → New MCP Server, or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"povio-ai-access": { "url": "https://prj-zw4fcvouv9mh.robodev.povio.dev/mcp" }
}
}
Any other MCP client
Add a remote HTTP (Streamable HTTP) server with the endpoint URL and let the client run the OAuth flow. A plain GET /mcp without Accept: text/html returns 405, because the endpoint only answers MCP POSTs. This page is what browsers and HTML-reading agents get.
Roles
| Role | Can do |
|---|---|
| employee | See their own seats and requests, and request access for themselves. |
| approver | Everything an employee can do, plus approve or decline requests, document review decisions, and run organization-wide read tools. |
| administrator | Everything: people, seats, provisioning, offboarding, provider sync, costs, members and settings. Administrators can also approve when the adminCanApprove setting is on. |
Your client lists every tool, whatever the user's role. Only call the tools in allowedTools from whoami. Any other tool returns status: 403 with the role it needs (for example "This action requires the administrator role"). Don't retry it. Tell the user which role they need instead.
Tools
Start here
| Tool | Role | What it does |
|---|---|---|
whoami | any | The signed-in user, their roles, and allowedTools. |
get_my_access | any | The user's own seats and requests (app tabs: My access, My requests). |
Read organization data
| Tool | Role | What it does |
|---|---|---|
search_people | approver, admin | Find people by name, email, department, type, tool, seat or lifecycle. Returns person ids and assignment ids. |
get_person_access | approver, admin | One person's active seats by name, email or id. |
get_access_summary | approver, admin | Counts of people and seats for a filter. |
list_requests / get_request | approver, admin | Access requests by status, tool or urgency, or one request by id. |
get_approval_queue | approver | All requests with their audit trail, plus the list of members (the Requests tab). |
list_access_reviews | approver, admin | Review signals: multiple tools, low usage, no tools, temporary access. |
get_usage_summary | approver, admin | Provider usage signals by tool or department. |
get_cost_summary | approver, admin | Seat costs, monthly API invoices, observed Codex charges. |
search_audit | approver, admin | Audit history search. |
get_data_freshness | approver, admin | Record counts and data source periods. |
get_admin_workspace | admin | Overview stats, settings, seat catalog, members, offboarding tasks, service accounts, review decisions, invoices, Slack outbox. Choose the sections you need. |
check_slack_status | admin | Whether the Slack bot, channel and approval routing work. |
Requests and approvals
| Tool | Role | What it does |
|---|---|---|
create_access_request | any (self), admin (anyone) | Request a new tool (add), a different seat (update) or a different tool (switch). Posts to Slack for approval. |
act_on_access_request | approver, admin | approve / decline a pending request; claim / done to provision it (admin). done updates the person's seats. |
Request lifecycle: pending → approved → claimed (provisioning) → done. A request can also be declined, or failed when automation needs a human.
People, seats and offboarding (administrators)
| Tool | What it does |
|---|---|
create_person | Add a person to People, with an employee membership. |
update_person | Edit the profile and email aliases, or archive or reactivate the person. Archiving creates removal tasks and closes open requests. |
reconcile_assignment | Correct or remove an existing seat directly, with a reason. |
complete_removal_task | Confirm a provider seat was removed for an offboarded person. |
sync_provider_seats | Reconcile Claude or Cursor seats against a provider member export. Preview first, then apply. |
Reviews, costs and settings
| Tool | Role | What it does |
|---|---|---|
save_review_decision | approver, admin | Record why an access pattern is OK, or for how long (for example two tools until a date). |
save_variable_cost | admin | Add, edit or archive a monthly usage-based invoice (for example Claude API). |
set_member_roles | admin | Enable or disable a member and set their roles. |
update_settings | admin | Organization settings (Slack, approval routing, reminders, adminCanApprove) and the seat catalog with prices. |
How to call the tools
Most write tools take their input as body. Tools that act on one record also take that record's id in params.id:
{
"name": "act_on_access_request",
"arguments": {
"params": { "id": "6f1c…-request-uuid" },
"body": { "action": "approve", "reason": "Team lead confirmed the need" }
}
}
{
"name": "create_access_request",
"arguments": {
"body": {
"subjectName": "Jane Doe",
"subjectEmail": "jane.doe@povio.com",
"changeType": "add",
"tool": "Claude",
"requestedSeat": "Standard",
"reason": "Daily coding work",
"urgency": "normal",
"durationType": "ongoing"
}
}
}
The read tools (search_people, list_requests and the others) take their filters as top-level arguments. Each tool's input schema in tools/list is the source of truth.
- Get ids from read tools: person and assignment ids from
search_people, request ids fromlist_requests, removal-task, review, catalog and invoice ids fromget_admin_workspace. - Money is in integer cents (
12500= $125.00). Dates areYYYY-MM-DD; invoice periods areYYYY-MM. - Tools are
Claude,CursorandCodex. Seat names must match an active catalog seat for that tool. - Errors come back as a tool result with
isError: trueand a JSON body that hasstatusandmessage. A409means the record changed or the action isn't allowed from its current state: re-read it and tell the user.
Rules for agents
- Writes are real and audited under the signed-in person's name. Many of them post to Slack. Confirm what you're about to do with the user before you approve, decline, complete, archive, sync or change roles or settings.
- Never approve on someone's behalf without their instruction. To record that a different approver made the decision, pass their email as
decisionMakerEmail. sync_provider_seats: always run it withapply: falsefirst, show the preview to the user, then apply.- Read before you write: check the current state (
get_request,get_person_access) instead of guessing ids or statuses.