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.
@dvcrn
Basic information
No overview available yet
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": ""
}
}
}
}Handle 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
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.
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.
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.
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.
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.
Define different command blocks in `context_servers` with unique `TOOL_PREFIX` values—one provided through the Zed extension, another via `npx` with environment variables.
It prefixes every Linear tool’s name (e.g., `workspace2_linear_create_issue`) to prevent naming conflicts when operating multiple workspaces.
A Go-based MCP (Model Control Protocol) connector for Jira that enables AI assistants like Claude to interact with Atlassian Jira. This tool provides a seamless interface for AI models to perform common Jira operations including issue management, sprint planning, and workflow tra
A server that integrates Linear's project management system with the Model Context Protocol (MCP) to allow LLMs to interact with Linear.
MCP server for Atlassian tools (Confluence, Jira)
Node.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.
Production-grade GitLab MCP server with 86 tools — full GitLab control from any AI agent (Claude, Cursor, Zed).
Comments