MCP clients

Connect your agent to selected tools without handing it provider credentials.

Codex CLI, Claude Code, and OpenCode have tested MCP setup paths. The client keeps its model loop and local environment; Alvoki authenticates the caller and decides which tools it can discover and invoke.

Client authorization and tool access

OAuth access and per-tool grants stay separate.

OAuth authorizes the MCP connection. The Agent identity then decides which tools the client can discover and invoke, with separate resource scope and Ask or Allow rules.

Codex CLI shown with active, separately revocable MCP OAuth authorization
The MCP client has its own revocable OAuth authorization for the Agent identity.
The same Agent identity with a GitHub tool limited by repository and branch
Each supplied tool gets its own resource scope and Ask or Allow rule.

Integration shape

See where the agent runs, which credentials it receives, and what Alvoki records.

Compatibility

Tested MCP registration and bearer-authenticated connectivity for Codex CLI, Claude Code, and OpenCode.

Credential path

The client receives a scoped Agent identity. Underlying provider credentials stay behind Alvoki.

Tool access

GitHub, package-backed tools, and imported MCP tools follow the grants on that identity, including approvals, expiry, and revocation.

Current scope

This provides authenticated MCP connectivity and controlled tool access, not a hosted model session or native IDE integration inside Alvoki.

First setup

Register one client, issue one Agent identity, and grant only the tools it needs.

Tested MCP clients

Choose your client. Keep the same per-tool controls.

These clients have tested registration and authenticated connectivity paths. Their commands differ; the Agent identity, per-tool grants, approvals, revocation, and activity records do not.

Tested MCP setup

Codex CLI

Register Alvoki as a Streamable HTTP MCP server and authenticate with the Agent identity credential.

Configure Codex CLI

Tested MCP setup

Claude Code

Register the remote HTTP endpoint with the Agent identity bearer header and keep Claude Code as the agent loop.

Configure Claude Code

Tested MCP setup

OpenCode

Configure the remote MCP endpoint and bearer authentication while the same Alvoki grants limit its tools.

Configure OpenCode

Related paths

Set up the client, then review what stays outside Alvoki.

MCP quickstart

Register a tested client, authenticate it, and grant its first tools.

Read more

Security model

Separate tools reached through Alvoki from access already available to the client or its machine.

Read more