MCP provider setup guides

Choose your provider guide

Use the provider links below for GitHub, Atlassian (Jira), Slack, Gmail, Google Drive, Google Docs, Google Calendar, Linear, Notion, Sentry and PostHog. Each guide covers the upstream account, the supported Durin setup path, review and activation, and client connection.

1. Prepare provider account access and any required OAuth client registration.
2. Save the installation in Durin, authorize the provider, discover and review tools, and complete the read test and activation.
3. Open the connection in your personal workspace, set up its connection URL, and add that URL to your MCP client.

Choose the available setup path

GitHub, Slack and Notion have built-in endpoint selection. The other named cards currently save drafts without an endpoint; their guides use Custom MCP with an explicit endpoint, subject to provider compatibility and deployment acceptance. Atlassian’s flat-tool and PostHog’s CLI/read-only profiles need query parameters that the form rejects, so those guides stop at a draft until reviewed runtime support exists.

The provider endpoint belongs in Durin setup. Your agent uses the personal Durin URL copied after setup. Directory presence and a successful sign-in alone do not establish that tools are ready.

For separate provider workspaces, use separate saved connections and distinct names in your agent. Each connection has its own conn_ ID.

Start with a reviewed read

Verify one allowed resource and confirm the identity, connection and execution outcome in activity. Reviewed production writes follow configured access and write policies.