MCP client setup

Before configuring the client

Your client connects to Durin; Durin then governs access to the configured upstream systems. Use a current client version that supports remote HTTP MCP and the required authorization flow. An administrator must have made at least one reviewed connection available to you before you can use its tools.

Sign in to the Durin personal workspace and confirm the account and organization. The endpoint belongs to that identity. A colleague’s endpoint, an upstream provider URL, and a guessed gateway base URL are not substitutes for your issued endpoint.

Find your personal MCP endpoint

Open Your MCP endpoint in the personal workspace. Use Set up your endpoint if prompted, then Copy URL or Copy configuration. Sign in to the client with the same Durin account. An endpoint URL is an identifier, not a credential.

Claude Code

Add Durin as a remote MCP server in your Claude Code configuration.

1. Open Claude Code settings or your MCP configuration file.
2. Add a new MCP server entry with the name "durin".
3. Set the transport to "http" and paste your Durin endpoint URL.
4. Save and restart Claude Code.

Cursor

Add Durin as an MCP server in Cursor's settings.

1. Open Cursor Settings and navigate to the MCP section.
2. Click Add MCP Server.
3. Enter "Durin" as the server name and paste your endpoint URL.
4. Select HTTP as the transport type.
5. Save the configuration.

OpenAI Codex

Configure Codex to use Durin as its MCP gateway.

1. Open your Codex MCP configuration.
2. Add Durin as a remote MCP server with your personal endpoint URL.
3. Authenticate when prompted during the first request.

Other MCP clients

Any MCP-compatible client that supports remote or HTTP MCP servers can connect to Durin. Use your personal endpoint URL and configure the appropriate transport. Exact syntax varies by client and version.

Use the configuration format your client accepts

Copy URL is appropriate when a client asks for a remote server address. Copy configuration gives you Durin’s JSON server entry for clients that accept that format. Check the client’s supported configuration format before pasting a full object into a URL field or a different configuration file.

The transport and authorization controls vary by client and version. If a client does not expose the expected remote-server flow, consult its own MCP setup instructions and confirm support before changing Durin policies. Do not put provider tokens into the Durin endpoint URL.

Verify discovery and your first read

Save the client configuration, authenticate as the endpoint owner, and inspect the available tools. Select a reviewed read for a resource that your connection permits.

1. Run one small read request from the client.
2. Open your Durin activity and locate the corresponding request.
3. Confirm your identity and the expected connection, then inspect the decision and execution outcome.
4. If authentication succeeds but a tool is missing, check personal provider consent, team access, and the installation’s reviewed tool status.

Change workspaces or reconnect deliberately

When changing the Durin account or workspace used by a client, copy the endpoint for the new context and authenticate again. Reusing an old endpoint with a different signed-in account will not transfer its ownership.

If access has been revoked, reconnecting the client does not restore organization membership or upstream consent. Ask the administrator or provider account owner to resolve the relevant restriction, then repeat the read check. Use the connection troubleshooting guide when the failure point is unclear.