Product and engineering

The Linear connector.

Issues and project tracking. Connect once with your own key. Every agent your team runs reads the same 8 tools under one permission model.

How access is governed

5

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

3

Write tools

Available through governed Slack workflows. MCP endpoints do not expose write tools.

0

Destructive tools

Linear defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Linear tool

8 tools, named as the agent sees them.

  • list_issuesread

    List Linear issues with optional filters.

  • get_issueread

    Get details of a specific Linear issue by ID or identifier (e.g., "ENG-123").

  • create_issuewrite

    Create a new Linear issue. Some teams may require explicit_instruction flag.

  • update_issuewrite

    Update an existing Linear issue.

  • add_commentwrite

    Add a comment to a Linear issue.

  • list_projectsread

    List Linear projects with progress and status.

  • get_team_summaryread

    Get a summary of a team's current workload: open issues, overdue, high-priority.

  • get_my_issuesread

    Get issues assigned to a specific user.

Use it from any agent

The same Linear tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Linear API Key in your Linear account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in product and engineering

CursorSentryAsanaClickUpNotionGitHub

Connect Linear once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in