Linear MCP Server Extension for Zed
@dvcrn
About Linear MCP Server Extension for Zed
No overview available yet
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-server-linear": {
"command": "npx",
"args": [
"-y",
"mcp-server-linear"
],
"env": {
"LINEAR_ACCESS_TOKEN": ""
}
}
}
}Tools
24Handle OAuth callback
Create a new issue in Linear
Create a new project with associated issues. Note: Project requires teamIds (array) not teamId (single value).
Update multiple issues at once
Edit an existing issue, updating any of its fields. Note: When setting projectMilestoneId, you must also set projectId.
Search for issues with filtering and pagination
Search for issues by their identifiers (e.g., ["ENG-78", "ENG-79"])
Get a single issue by identifier, including all comments
Get all teams with their states and labels
Get current user information
Delete an issue
Get project information
List all projects or filter them by criteria
Create multiple issues at once
Creates a new comment on an issue
Updates an existing comment
Deletes a comment
Resolves a comment
Unresolves a comment
Creates a new customer need from an attachment
Get milestones for a project with filtering and pagination
Create a new project milestone
Update a project milestone
Delete a project milestone
Overview
What is Linear MCP Server Extension for Zed?
Linear MCP Server Extension for Zed integrates a Linear MCP Server into Zed's AI Assistant, enabling direct interaction with Linear through Zed. It is designed for Zed users who want to manage Linear issues, projects, and comments without leaving their editor.
How to use Linear MCP Server Extension for Zed?
Obtain a Linear API key (developer token or personal API key) and add it to Zed's settings.json under the context_servers field with the key mcp-server-linear. Optionally set a tool_prefix for multiple workspace support. You can also configure the extension directly in an Agent profile.
Key features of Linear MCP Server Extension for Zed
- Full Linear API integration through MCP
- Create, update, and manage issues directly from Zed
- Comment management (create, update, delete, resolve)
- Project and milestone management
- Multiple workspace support with tool prefixes
- Advanced issue search and filtering
- Label management and parent/child issue relationships
Use cases of Linear MCP Server Extension for Zed
- Creating and updating Linear issues while coding in Zed
- Managing issue comments, labels, and relationships from the AI Assistant
- Searching and filtering issues across workspaces
- Handling projects and milestones without switching context
- Working with multiple Linear workspaces simultaneously
FAQ from Linear MCP Server Extension for Zed
How do I get a Linear API key?
You can create a developer token from Linear's Workspace Settings > API > OAuth application, or a personal API key from Personal Settings > API > Personal API Keys.
How do I configure the extension in Zed?
Add your API key to Zed's settings.json under context_servers with the key mcp-server-linear and the setting linear_api_key. An optional tool_prefix can distinguish workspaces.
Can I use multiple Linear workspaces?
Yes, by using the optional tool_prefix setting to prefix all Linear tool names (e.g., company1_linear_create_issue) so tools from different workspaces are clearly separated.
How do I run multiple instances simultaneously?
Define different command blocks in context_servers with unique TOOL_PREFIX values—one provided through the Zed extension, another via npx with environment variables.
What does the tool_prefix setting do?
It prefixes every Linear tool’s name (e.g., workspace2_linear_create_issue) to prevent naming conflicts when operating multiple workspaces.
Frequently asked questions
How do I get a Linear API key?
You can create a developer token from Linear's Workspace Settings > API > OAuth application, or a personal API key from Personal Settings > API > Personal API Keys.
How do I configure the extension in Zed?
Add your API key to Zed's `settings.json` under `context_servers` with the key `mcp-server-linear` and the setting `linear_api_key`. An optional `tool_prefix` can distinguish workspaces.
Can I use multiple Linear workspaces?
Yes, by using the optional `tool_prefix` setting to prefix all Linear tool names (e.g., `company1_linear_create_issue`) so tools from different workspaces are clearly separated.
How do I run multiple instances simultaneously?
Define different command blocks in `context_servers` with unique `TOOL_PREFIX` values—one provided through the Zed extension, another via `npx` with environment variables.
What does the tool_prefix setting do?
It prefixes every Linear tool’s name (e.g., `workspace2_linear_create_issue`) to prevent naming conflicts when operating multiple workspaces.
Basic information
More Version Control MCP servers
🚀 GitLab MR MCP
kopfrechnerInteract seamlessly with GitLab repositories to manage merge requests and issues. Fetch details, add comments, and streamline your code review process with ease.
GitHub MCP Server Extension for Zed
LoamStudiosA GitHub MCP Server extension for Zed
mcp-github-trending MCP Server
hetaoBackendMCP server for getting github trending repos & developers
GitHub Actions 工作流使用说明
HenryHaosonYuque mcp server
MCP Git Ingest
adhikaspA Model Context Protocol (MCP) server that helps read GitHub repository structure and important files.
Comments