Oakallow MCP Server

Oakallow MCP Server

Runtime permission, approval, and audit governance for AI agent tool execution.

Oakallow is a hosted remote MCP server. It sits between an agent and the actions it wants to take, so that a specific action can be checked, gated behind human approval when it is risky, authorized with a single-use signed token, and recorded in an immutable audit log — at the moment of execution.

• Website: https://oakallow.com
• MCP endpoint: https://api.oakallow.io/mcp (Streamable HTTP)
• OAuth 2.1 compliance: https://oakallow.com/docs/oauth
• MCP protocol details: https://oakallow.com/docs/mcp

What this connector is for

Oakallow injects a governance checkpoint into a workflow that may also use other connectors. An agent does its investigative work (for example, looking up an account through another connector), forms a recommendation, and calls Oakallow to request approval for the action. A human approver then decides in the Oakallow dashboard or mobile app, under enforced multi-factor authentication.

The connector is a requester and pass-through, not a decider:

• It can list your tools, check permissions, request approvals, and mint run tokens once an action is approved.
• It cannot approve or deny on a human's behalf. Decisions happen on a separate, MFA-bound surface (the dashboard), never over the connector.

Standard tools

* check_permission returns a read-only verdict, but checking an unregistered tool has a side effect by design: Oakallow auto-creates a gated draft entry for that tool (with conservative, fail-closed defaults) so the eventual call is governed and the owner can triage it from the dashboard. A requires_approval verdict also creates an approval request. This is intentional — an unknown tool is never silently trusted.

Connecting

Add https://api.oakallow.io/mcp as a custom connector in your MCP client (Claude, Claude Desktop, Cowork, ChatGPT, or any Streamable HTTP MCP host). You will be redirected to sign in to Oakallow and approve the requested scopes:

• mcp:read — list tools, view pending approvals, check permissions, read activity.
• mcp:write — create approval requests and mint run tokens.

See examples/ for a Claude Desktop config and an OAuth flow walkthrough.

How a governed call works

1. The agent calls Oakallow with its credential.
2. Oakallow resolves the permission rule for the specific tool, tenant, and resource.
3. If the action is allowed, Oakallow mints a single-use, HMAC-signed run token.
4. If approval is required, an approval request is created and a human is notified. The agent's call is held until the request is decided or expires.
5. The agent uses the run token to perform the action; Oakallow writes an immutable audit row capturing the outcome.

Oakallow lives outside the execution path. It governs and records what was reported; it does not run your tools or receive your tool parameters beyond a PII-scrubbed reason.

License

See LICENSE.

Changelog

See CHANGELOG.md.

---

© Islemonics Studios LLC. Patent pending.