One route for MCP access.
Connect your agents to company tools through Durin, with your rules checked before a request runs.
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.
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 configuration with the value from your endpoint.
Get your MCP endpointRun in your terminal:
Open Claude Code and use /mcp to authenticate Durin.
Then request a tool through Durin and confirm the session in Connected clients.
Configuration for Claude Code
~/.claude.json
Merge the Durin entry into your existing configuration.
Durin governs requests sent through its gateway. Direct API calls, browser actions and local shell commands need separate controls.
MCP connects agents to your systems.
Model Context Protocol is an open standard for connecting AI applications to tools, data and reusable prompts.
Read the MCP Architecturetools/listDiscover available tools
An MCP server advertises the tools an agent can request.
tools/callRequest an action
The client sends a tool name and structured arguments.
result / errorReceive the result
The server returns content or an error to the client.
A shared protocol. Your access decisions.
- Reuse integrations across clients
- One compatible MCP server can serve multiple agent clients, reducing separate integration work.
- Control what those agents can do
- With Durin, route supported requests through identity checks, access policies, independent approvals and an audit record.