Ondi MCP Overview
Ondi MCP lets MCP-compatible AI clients call reviewed Ondi tools with an existing Ondi API key. It does not create a separate authentication system.
The API key keeps the same access as the Ondi user who created it. Backend roles, permissions, tenant context, and audit logging still apply.
Setup
- Open Ondi settings and go to API Keys.
- Create an API key.
- Enable MCP / AI tools for the key.
- Add the MCP server URL to your MCP-compatible client.
- Store the API key only in the client secure config, an environment variable, or a secret manager.
MCP Server URL
Use the environment-specific Ondi MCP URL shown in the API Keys MCP Setup tab.
For Supabase-hosted environments, the URL format is:
https://<project-or-api-domain>/functions/v1/mcp
Permissions
The AI client can only do what the API key owner can do in Ondi. Tenant-scoped keys do not need a tenant ID in tool calls; Ondi injects the authenticated tenant context.
Current MVP Tools
The first MCP release exposes a small reviewed delivery tool set:
- List deliveries
- Get delivery
- Create delivery
- Update delivery
- Cancel delivery
Write and destructive tools are marked for client confirmation.