Quickstart guide

Before you begin

Choose whether you are creating a workspace or joining one that already exists. A new workspace needs an administrator who can complete organization onboarding, payment setup, and provider consent. A member joining an existing workspace needs an accepted invitation and a verified account linked to that organization.

• Have an MCP client that supports the remote HTTP connection and authentication flow used by Durin.
• Choose a provider account and a harmless read operation you are allowed to perform.
• Confirm which workspace and environment you intend to use. Keep sandbox learning separate from production activation.

Create your account

Sign up at the Durin app. You will be asked to name your organization and complete onboarding.

1. Go to the Durin sign-up page and create an account.
2. Name your organization — this becomes your workspace.
3. Complete the onboarding questions, payment setup, and workspace preparation. Payment setup alone does not enable a provider.

Add your first connection

A connection defines an upstream system that your agents can access through Durin. An administrator installs it; members can request access. Use the public MCP simulator to try the request flow before setup.

1. As an administrator, open Connections in the Admin workspace.
2. Choose a provider or a custom MCP server from the directory and save its setup.
3. Sign in to the provider, discover tools, review permissions, and complete the read-only readiness test.
4. Enable only after the setup guide confirms readiness and you accept the current billing preview. A saved draft is not active.

Connect your MCP client

Point your AI client at your personal Durin MCP endpoint so requests flow through the gateway.

1. Copy your personal MCP endpoint from the Durin app.
2. Open your MCP client settings (Claude Code, Cursor, Codex, or another client).
3. Add Durin as a remote or HTTP MCP server and paste the endpoint URL.
4. Authenticate when prompted.

Run your first request

Start with a read-only tool call to verify the end-to-end path before trying writes.

1. In your MCP client, choose a reviewed read tool and a resource shown as allowed for your connection.
2. Check the Durin activity log to see the identity, policy decision, and result.
3. Check the execution outcome as well as the policy decision; an allow decision alone is not proof of upstream success.

Confirm the first request worked

A successful connection is more than a saved URL. Check the complete path from the client to the intended resource and back.

1. Confirm the client has authenticated and can discover the expected reviewed tool.
2. Run one read against a resource listed as allowed for the connection.
3. Open your activity in Durin and match the user, connection, tool, and time to that request.
4. Verify both the decision and execution outcome. Keep a failure or uncertain outcome open for investigation rather than treating the allow decision as success.

If setup stops at a checkpoint

Use the first incomplete step in the connection setup guide to decide what to do next. Missing consent needs the provider account holder; missing membership or team access needs a Durin administrator; a validator or provider-acceptance blocker cannot be fixed by repeatedly clicking Enable.

For client authentication errors, copy the endpoint again and check that the client signs in as its owner. If the client connects but no tool is available, check installation state, tool review, personal provider access, and team assignment. Keep the connection disabled until the required checks succeed.