Linear MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment mode for running the server | production |
| LOG_LEVEL | No | Sets the logging level (e.g. DEBUG for detailed logs) | INFO |
| LINEAR_API_KEY | Yes | Your Linear API key (should start with 'lin_api_') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_issuesC | List Linear issues (also called tickets) with filtering by assignee, status, and project. Use this to browse and find issues in your Linear workspace. |
| get_issueC | Get detailed information about a specific Linear issue (also called a ticket), including comments if requested. |
| list_membersC | List Linear team members with optional filtering by name. This tool is useful for finding member details including usernames, display names, and emails. |
| list_projectsB | List Linear projects with optional filtering by team, name, and archive status. Shows project details including status, lead, progress, and dates. |
| get_projectB | Get detailed information about a Linear project including team, lead, issues, and members. Use this to see comprehensive details of a specific project. |
| list_teamsA | List Linear teams with details about their members, projects, and issues. Use this to get a high-level view of all teams in your Linear workspace. |
| add_commentB | Add a comment to a specific Linear ticket. This tool is useful for providing feedback, status updates, or additional information on existing tickets. |
| create_issueB | Create a new issue in Linear. This tool is useful for adding new tasks, bugs, or feature requests to your Linear workspace. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose targeting specific resources and actions in Linear, such as adding comments, creating issues, getting issues/projects, and listing issues/members/projects/teams. There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one based on the task.
All tool names follow a consistent verb_noun pattern (e.g., add_comment, create_issue, get_issue, list_issues), with verbs like 'add', 'create', 'get', and 'list' applied uniformly to appropriate nouns. There are no deviations or mixed conventions, ensuring predictable and readable naming throughout.
With 8 tools, this server is well-scoped for managing Linear issues, projects, teams, and members. Each tool earns its place by covering essential operations like CRUD for issues and listing for resources, without being too sparse or bloated, making it efficient for typical workflows.
The tool set provides strong coverage for core Linear operations, including creating and retrieving issues, adding comments, and listing issues, members, projects, and teams. However, minor gaps exist, such as missing update or delete operations for issues and projects, which agents might need to work around for full lifecycle management.