MCP client setup
Set up Claude Code, Codex or Cursor with the Durin CLI or a remote MCP endpoint, authorize access, and verify a reviewed tool call.
Guided setup with your Agent
Run npx @accessdurin/cli interactively or paste the homepage setup prompt into your Agent. Complete login or signup, organization onboarding, payment setup if required, and separate MCP consent.
The CLI preserves existing settings, stores credentials in the OS credential store, and configures and verifies an organization-bound stdio connection. Reopen your harness when prompted. Check it with npx @accessdurin/cli verify; use tools list or tools call for terminal access.
CLI 1.1.0 is awaiting release. It adds automatic skills, hook setup, Gemini CLI, GitHub Copilot CLI, custom harnesses, and Homebrew, Ubuntu/Debian and Windows installation.
Hooks use an existing Endpoint helper for Claude/Codex or a custom checker. Setup does not install Endpoint or enroll reporting; MCP verification does not verify hook execution.
Manual remote HTTP setup
Copy Your MCP endpoint, or the connection URL for one installation. Replace PASTE_YOUR_COPIED_DURIN_URL below and use a distinct server name per connection. Direct HTTP requires its own authorization grant.
- Claude Code: claude mcp add --transport http --scope user durin-notion-engineering "PASTE_YOUR_COPIED_DURIN_URL". Open /mcp and authenticate.
- Codex: codex mcp add durin-notion-engineering --url "PASTE_YOUR_COPIED_DURIN_URL", then codex mcp login durin-notion-engineering.
- Cursor: merge { "mcpServers": { "durin-notion-engineering": { "url": "PASTE_YOUR_COPIED_DURIN_URL" } } } into ~/.cursor/mcp.json, preserving existing servers. Enable the entry and authenticate.
Verify access
Authenticate as the URL’s owner. Refresh tools: the client shows four Durin tools. Ask it to list your connections with durin_list_connections, find a reviewed read with durin_list_tools, run it on an allowed resource with durin_call_tool, and inspect its activity outcome. Browser sign-in alone does not authenticate an MCP client.
Troubleshooting
Authentication works but tools are missing
Check enabled installation status, reviewed validators, team access and personal provider consent. Refresh after correcting the failing checkpoint.
Frequently asked questions
Can I reuse authentication for a different URL?
No. Authenticate each exact endpoint separately; full-gateway and sibling-connection tokens are not interchangeable.