MCP client setup

Guided setup with your Agent

Run pnpx @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 pnpx @accessdurin/cli verify; use tools list or tools call for terminal access.

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, run one reviewed read on an allowed resource, and inspect its activity outcome. Browser sign-in alone does not authenticate an MCP client.