Zed MCP Server Linear

🚀 Linear MCP Server Extension for Zed

This extension integrates My Linear MCP Server into Zed's AI assistant, enabling direct interaction with Linear through Zed.

🚀 Quick Start

This extension seamlessly integrates the Linear MCP Server into Zed, allowing you to interact directly with Linear within the Zed environment.

✨ Features

• ✨ Comprehensive Linear API integration via MCP
• 🔄 Create, update, and manage issues directly from Zed
• 📝 Comment management (create, update, delete, resolve)
• 📊 Project and milestone management
• 👥 Multi-workspace support
• 🔍 Advanced issue search and filtering
• 🏷️ Label management
• 📎 Parent/child issue relationships

📦 Installation

Option 1: Developer Token

1. Access Linear: Workspace Settings > API > OAuth Applications > Create or select an application (e.g., "Cline MCP").
2. Under "Developer Tokens", click "Create and copy token".
3. Select "Application" as the operator and copy the generated token.

Option 2: Personal API Key

1. Access Linear: Your Personal Settings > API > Personal API Keys.
2. Click "Create key", give it a label (e.g., "Cline MCP"), and copy the generated key.

Setup in Zed

Get the key you just received and add it to the "context_servers" field in Zed's settings.json file:

{
  "context_servers": {
    "mcp-server-linear": {
      "settings": {
        "linear_api_key": "<LINEAR_API_KEY>",
        "tool_prefix": "<Optional tool prefix>"
      }
    }
  }
}

You can also add these keys directly to a proxy configuration file, for example:

{
  "assistant": {
    "profiles": {
      "write": {
        "name": "Write",
        "context_servers": {
          "mcp-server-linear": {
            "settings": {
              "linear_api_key": "<LINEAR_API_KEY>",
              "tool_prefix": "company1" // Optional
            }
          }
        }
      }
    }
  }
}

💻 Usage Examples

Multi-workspace Support

If you use multiple Linear workspaces, you can use the optional "tool_prefix" setting to prefix all Linear tools. This helps distinguish between different workspaces:

{
  "context_servers": {
    "mcp-server-linear": {
      "settings": {
        "linear_api_key": "<LINEAR_API_KEY>",
        "tool_prefix": "company1"
      }
    }
  }
}

With this configuration:

• Tool names will be prefixed (e.g., "company1_linear_create_issue").
• Clearly distinguish which workspace each tool is operating on.
• Prevent conflicts when working with multiple Linear instances.

Multiple Simultaneous Installations

You can run multiple instances of the Linear MCP Server by configuring different command blocks and using unique "TOOL_PREFIX" values:

{
  "context_servers": {
    "mcp-server-linear": {
      // Provided by the Zed extension
      "settings": {
        "linear_api_key": "<LINEAR_API_KEY>",
        "tool_prefix": "company1"
      }
    },
    "linear-workspace2": {
      // Provided by npx
      "settings": {},
      "command": {
        "command": "npx",
        "args": ["-y", "mcp-server-linear"],
        "env": {
          "LINEAR_ACCESS_TOKEN": "<LINEAR_API_KEY_2>",
          "TOOL_PREFIX": "workspace2"
        }
      }
    }
  }
}

Each instance will prefix tools with the specified "TOOL_PREFIX", allowing you to interact with multiple Linear workspaces simultaneously.