durin
Book A Demo
Knowledge base
Connections & MCP

How to add Linear MCP

Connect Linear through its named card in Durin and verify an allowed read and a denied write before rollout.

Admin · Member2 min readUpdated

Prepare Linear access

Use the named Linear card with https://mcp.linear.app/mcp, the read-write endpoint. Durin registers its own OAuth client, so no client ID or secret is needed. Each authorization covers one workspace, and its scopes apply to the whole workspace.

Save, review and enable

Open Admin → Connections → All providers and choose Linear. Keep Register automatically and leave OAuth scopes blank. Save the draft, sign in, discover tools, save permission review and obtain the matching deployed validator. Run an approved read test, review billing, confirm activation and enable the reviewed tools.

Review every tool that is not read-only as a write: the save tools can update existing objects, and the diff tools act on the linked GitHub repository. To make writes impossible upstream, add https://mcp.linear.app/mcp/readonly as a Custom MCP server instead.

Complete personal provider access, copy your Durin connection URL and authenticate your MCP client for that exact URL.

Read and comment on a test issue

In a dedicated test team, read one issue with get_issue and its identifier, such as DQA-1. Add one comment to it with save_comment, passing only issueId and body. Never pass id or parentId: Linear then ignores issueId and edits or replies to another comment.

  • Expected success: the issue details, then one new comment on that issue; activity records both executions.
  • Expected denial: configure Durin to deny writes and repeat the comment; save_comment leaves discovery and no new provider dispatch occurs. Reads continue.

Troubleshooting

Sign-in succeeds but a tool is unavailable

Check that Linear consent granted write access, then personal consent, permitted resources, deployed validator and activation. Discovery alone does not grant access.

Frequently asked questions

What should I record?

Record client, version, UTC date, tool/schema revision and both activity IDs when you complete the workflow.

Try Durin with your MCP workflow.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.