Linear

Connect Linear to collect ticketing evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Linear:

   1. In Linear, go to Settings › Account › Security & Access and create a personal API key.
   2. Restrict the key to the Read permission instead of full access, and optionally limit it to specific teams.
   3. Create the key and copy it.

   Admins control whether members can create API keys under Settings › Administration › API › Member API keys (admins can always create them). The docs don't name the create button or say whether the key is shown once. No base URL or workspace ID is needed for Linear's API.

   Source: linear.app, checked 2026-10-07.

2. On Compliance › Connectors, open Linear, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Connect with the MCP server

Choose MCP server: the address https://mcp.linear.app/mcp is filled in. Sign in to Linear when asked. It lets Griffin AI search Linear; the compliance evidence comes from the API token connection.

Frameworks

Safeguard's automated tests read Linear and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Ticketing connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks