Set up Durin in your MCP client.

Connect Claude Code, Codex, Cursor, your own MCP server, or a custom harness to the Durin gateway with a personal MCP endpoint.

Try the MCP simulator

▣ ✻ Claude Code

Try an MCP request.

See what an agent is allowed to do. Run a sample MCP request through Durin’s policy checks without an account or API key.

Claude Code v2.1.278

Fable 5.1 with high effort · Claude Max

/Users/durin

⚠ 1 MCP server needs authentication · run /mcp

YouPrompt
Read the engineering handbook through Durin and summarize the release rule.
ClaudeThinking
I need the handbook. I will call the governed MCP tool and let Durin check identity, policy, and scope first.
Tool useMCP call
mcp__durin__sandbox__read_document({ "resource": "engineering/handbook", "durinIdempotencyKey": "demo-read-001" })
Durin MCPPolicy check
ALLOW: Policy matched an approved read. No approval required.
Tool resultSandbox response
Synthetic handbook: Engineering changes require a review before release.
ClaudeFinal answer
The handbook says engineering changes require review before release.

Reasoning and Tool Trace

Trace pane

Step	Event	Detail
01	Goal	Read the engineering handbook through Durin and summarize the release rule.
02	Plan	I need the handbook. I will call the governed MCP tool and let Durin check identity, policy, and scope first.
03	Boundary	Durin evaluates identity, connection state, resource policy, and approval before dispatch.
04	Outcome	Policy matched an approved read. No approval required.

Step	Event	Detail
01	user	Read the engineering handbook through Durin and summarize the release rule.
02	assistant.reasoning	I need the handbook. I will call the governed MCP tool and let Durin check identity, policy, and scope first.
03	assistant.tool_call	mcp__durin__sandbox__read_document({ "resource": "engineering/handbook", "durinIdempotencyKey": "demo-read-001" })
04	tool.result	Synthetic handbook: Engineering changes require a review before release.
05	assistant.final	The handbook says engineering changes require review before release.

Step	Event	Detail
01	Client	Claude Code requested sandbox__read_document
02	Identity	Identity active for demo_member in the organization.
03	Connection	Engineering workspace is enabled and verified.
04	Approval	not required for this read
05	Dispatch	Durin dispatched the approved tool call to the sandbox fixture.
06	Result	Synthetic handbook: Engineering changes require a review before release.

Reasoning summaries, LLM messages, and MCP tool calls advance with the terminal so IT can see where Durin allows, pauses, or blocks access.

Install Durin to your Agent

Copy a setup prompt into your Agent, or choose your client for manual setup.

Let your Agent set it up

Copy this prompt into your Agent. It runs the Durin CLI and guides setup. You choose your organization and Agent in the CLI and complete sign-in in the browser.

Set up Durin for my current Agent using pnpx @accessdurin/cli in an interactive terminal.

Guide me through login or signup and organization onboarding, then select my Agent in the CLI. Complete the MCP setup for that organization. Pause for my account choices, browser sign-in, any required payment setup, and MCP consent. Preserve my existing settings.

Run pnpx @accessdurin/cli verify, report the result, and tell me to reopen my Agent. If an interactive terminal is unavailable, give me the command to run myself.

Set up Durin for my current Agent using pnpx @accessdurin/cli in an interactive terminal.

Guide me through login or signup and organization onboarding, then select my Agent in the CLI. Complete the MCP setup for that organization. Pause for my account choices, browser sign-in, any required payment setup, and MCP consent. Preserve my existing settings.

Run pnpx @accessdurin/cli verify, report the result, and tell me to reopen my Agent. If an interactive terminal is unavailable, give me the command to run myself.

Manual setup

Choose your client and configure a direct MCP connection.

Use your personal endpoint

Copy your endpoint from Connected clients in Durin. Replace YOUR_PERSONAL_ENDPOINT_ID in the example with the value from your endpoint.

Get your MCP endpoint

Add the configuration in your client settings.

Run opencode mcp auth durin to authenticate.

Then request a tool through Durin and confirm the session in Connected clients.

Configuration for OpenCode

~/.config/opencode/opencode.json

Merge the Durin entry into your existing configuration.

Point the client at Durin, not at every tool.

Durin gives each user a personal MCP endpoint. Add that endpoint to the client you control, sign in with the same Durin account, and route approved tools through the gateway.

Copy your Durin endpoint

Copy Your MCP endpoint for all your available connections, or open one personal connection and choose Set up connection URL, then Copy connection URL. Authenticate the client for that exact URL with the owning Durin account.

Add Durin as an MCP server

In Claude Code, Codex, Cursor, or a custom harness, choose the remote or HTTP MCP server option when your client exposes one and paste the Durin endpoint.

Verify a reviewed read

Run one reviewed read and confirm the identity, connection, policy decision and execution outcome in Durin activity. Reviewed production writes follow the configured policy; request Durin sandbox from Connections to learn approval flows with synthetic data after admin approval.

Connect your MCP client to Durin.

Create an account to copy your personal MCP endpoint, add it to your client, and inspect governed requests.

Create an account