đŸ’ģ

Linear

Query and manage Linear issues, projects, and team workflows.

Category: Developer
Difficulty: Medium

Quick Configuration

Choose the setup that matches your environment.

Before You Start

  • Confirm you have the account, endpoint, or API key required for Linear.
  • Start with minimum scopes and read-only access where possible.
  • Keep secrets in environment variables instead of hardcoding them in JSON.

Hosted / Remote

JSON
Hosted Config json
{
  "linear": {
    "url": "https://YOUR_LINEAR_MCP_ENDPOINT"
  }
}

Local CLI (npx)

JSON
Local Config json
{
  "linear": {
    "command": "npx",
    "args": ["-y", "mcp-remote", "https://YOUR_LINEAR_MCP_ENDPOINT"],
    "env": {
      "LINEAR_API_KEY": "YOUR_LINEAR_API_KEY"
    }
  }
}

Common Pitfalls & Fixes

  • âš ī¸ Watch out: API token scopes and mapping between teams, projects, and cycles.
  • 🔑 Always store API keys in environment variables, never hardcode them in JSON.
  • đŸ›Ąī¸ Start with read-only scopes if available to verify connection safely.

Example Prompts

Once connected, try these prompts to test capabilities:

  • List issues assigned to me due this week and summarize priorities.
  • Find blockers across the current cycle and propose a resolution plan.
  • Create a new issue titled "Investigate build failure" and assign it to me.

Verification Checklist

  • Run 1-2 real prompts to confirm Linear returns usable data.
  • Check that error messages are clear enough for troubleshooting.
  • Document the required scopes, dependencies, and env vars for future reuse.