Skip to content

Linear

Manage issues, projects, and team workflows in Linear.

FamilyCategorySub-typeAuth typeTrending score
Productivityproductivityissue-trackingbearer_token80

Overview

Product URLAPI docsSupported features
https://linear.app/https://linear.app/docs/api-and-webhookstool_discovery, health_check, approval_gated_writes

Setup

  1. Install the connector instance.
  2. Store the provider token or connection secret.
  3. Sync the tools and test the connection.
  4. Review approval-gated write tools before running them.

Auth & Configuration

This connector does not require additional instance config.

Available Tools

ToolRequires approvalDescription
list_projectsNoList Linear projects.
list_issuesNoList Linear issues with optional team or project filters.
get_issueNoRetrieve a single issue by ID.
create_issueYesCreate a new Linear issue.
update_issueYesUpdate an existing Linear issue.

Use list_projects for the main execution example below because it is safe to run without approval.

Examples

Install

bash
chainabit connectors install linear --name "Linear"
bash
curl -X POST "$BASE_URL/connectors/instances" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "connectorKey": "linear",
  "displayName": "Linear"
}'
javascript
const response = await fetch(`${BASE_URL}/connectors/instances`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "connectorKey": "linear",
  "displayName": "Linear"
}),
});

Credentials

bash
chainabit connectors auth <instance-id>
bash
curl -X POST "$BASE_URL/connectors/instances/<instance-id>/credentials" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "credType": "bearer_token",
  "credentials": {
    "token": "YOUR_BEARER_TOKEN"
  }
}'
javascript
await fetch(`${BASE_URL}/connectors/instances/<instance-id>/credentials`, {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${TOKEN}`,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "credType": "bearer_token",
  "credentials": {
    "token": "YOUR_BEARER_TOKEN"
  }
}),
});

Execute

bash
chainabit connectors exec <instance-id> list_projects --input '{}'
bash
curl -X POST "$BASE_URL/connectors/instances/<instance-id>/tools/tool_list_projects/execute" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {}
}'
javascript
const response = await fetch(
  `${BASE_URL}/connectors/instances/<instance-id>/tools/tool_list_projects/execute`,
  {
    method: 'POST',
    headers: {
      Authorization: `Bearer ${TOKEN}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
  "input": {}
}),
  },
);

Security Notes

  • Keep tokens, API keys, and connection strings in the encrypted credentials vault.
  • Do not allow arbitrary server URLs for remote MCP connectors.
  • Mutating tools are approval-gated. Review the payload before executing them.

Troubleshooting

  • If the health check fails, verify the token scope or credential payload and try again.
  • If the tool list is empty, re-run sync-tools after storing the latest credentials.

Back to the catalog

Built with purpose.