durin
Sign up

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

Add Durin as a remote MCP server

{
  "mcpServers": {
    "durin": {
      "transport": "http",
      "url": "https://mcp.getdurin.com/mcp/u/{id}"
    }
  }
}

Use the exact personal endpoint shown in Durin. Client configuration names and transport labels vary by version.

Run a sample MCP request

Choose the MCP client path.

Use the personal Durin endpoint from the app, then add it to the client or harness that will send governed tool requests.

Your MCP serverClaude CodeCodexCursorCustom harness
Open the MCP simulator

Client setup depends on each tool's remote MCP support.

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

Use the exact personal MCP URL shown in the Durin app. Keep the endpoint tied to the workspace and user that will run the client.

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.

Run a read before writes

Start with a read-only tool call. Confirm the request, identity, policy decision, and result in Durin before testing writes or approval flows.

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

Production connections use provider setup and trust review.