Integrations

Connect agents to tools without exposing provider credentials.

Start with GitHub and MCP clients, where setup, credential custody, and outputs are easiest to inspect. The tested MCP setup path today covers Codex CLI, Claude Code, and OpenCode.

Get started Start with GitHub

Integration shape

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

Available today

GitHub access plus tested MCP registration and bearer-authenticated connectivity for Codex CLI, Claude Code, and OpenCode.

Agent loop

An ExecWarden-hosted session or the connected client owns the reasoning loop. A separate execution environment supplies machine access when needed.

Credentials

Provider credentials can stay in ExecWarden instead of being copied into the agent environment.

Tool controls

GitHub, package-backed tools, and imported MCP tools can use per-tool grants, approvals, expiry, revocation, and activity records.

First setup

Pick one client or provider and a concrete task whose access and output are easy to inspect.

One access model

Start with a client or provider whose access and output are easy to inspect.

Across GitHub, MCP clients, and package-backed tools, provider credentials can stay behind ExecWarden. Agents receive scoped access, selected actions can pause for approval, and calls through ExecWarden leave activity records.

MCP clients

Codex CLI, Claude Code, OpenCode, and other compatible MCP clients.

Use ExecWarden's MCP endpoint to give the client a scoped Agent identity and a selected set of tools.

GitHub

The first concrete system to try.

Repo allowlists, branch patterns, PR review, separate merge authority, approvals, and activity records make the access easy to inspect.

Packages and imported MCP

Add internal APIs and SaaS tools with the same controls.

Package-backed tools and imported MCP tools can use the same scoped grants, approvals, and activity records.

Where teams start

Concrete first integrations to try.

1GitHub access limited to selected repositories and branch patterns.

2Linear issue updates through a package-backed tool with its own grant.

3Imported MCP tools selected separately for each Agent identity.

Setup paths

Choose the client, provider, or execution path you need.

Start with a client or provider whose access is easy to inspect.

GitHub and MCP clients are usually the clearest first proof because the inputs, outputs, and credentials are easy to inspect.

Start with GitHub Read docs