Secure MCP gateway

Give MCP clients capabilities, not your underlying credentials.

Codex CLI, Claude Code, and OpenCode can connect to ExecWarden through a tested MCP setup path.

Product proof

OAuth authorization and tool authority stay separate.

OAuth controls the MCP transport. The named Agent identity and its per-tool grants control what the client can actually do.

Codex CLI shown with active, separately revocable MCP OAuth transport authorization
Codex CLI has its own revocable OAuth transport authorization for the Agent identity.
The same Agent identity with a GitHub capability limited by repository and branch
The same identity gets a separate Ask or Allow decision and resource scope for each tool.

Integration shape

The setup, credentials, governed actions, and evidence should be obvious.

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 ExecWarden.

Governed actions

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

Not implied

This is governed MCP connectivity and tool access, not a hosted model session or native IDE integration inside ExecWarden.

Start

Register one client, issue one Agent identity, and grant one bounded tool set.

How access is decided

Connect supported MCP clients without handing over provider tokens.

MCP authentication identifies the caller. Per-tool grants decide what it can discover and invoke.

Tested connectivity

Use the MCP path that is grounded today.

The grounded path today is an ExecWarden MCP setup for supported local clients, not a hosted model session inside ExecWarden.

Client identity

Name the caller before it acts.

A local agent, hosted session, or remote runtime acts through an Agent identity that can expire, be disabled, or be revoked.

No broad token copy

Keep provider credentials behind the gateway.

The agent receives a scoped MCP credential, not the raw provider token stored by ExecWarden.

Where teams start

Ways teams start with governed MCP access.

1Codex connected to ExecWarden MCP for a repo-review identity.
2Claude Code configured with a scoped MCP identity.
3OpenCode connected for read-only capability discovery.

Connect an MCP client

Register one client and grant one bounded tool set.

Start with the tested MCP setup path for the client you already want to use, then grant only the tools the task needs.

Connect an MCP clientRead MCP quickstart