Skip to main content
Glama
wkoutre

Linear MCP Server

by wkoutre

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LINEAR_API_KEYYesYour Linear API key for authentication

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

NameDescription
linear_getViewerA

Get information about the currently authenticated user

linear_getOrganizationA

Get information about the current Linear organization

linear_getUsersA

Get a list of users in the Linear organization

linear_getLabelsB

Get a list of issue labels from Linear

linear_getTeamsB

Get a list of teams from Linear

linear_getWorkflowStatesB

Get workflow states for a team

linear_getProjectsB

Get a list of projects from Linear

linear_createProjectC

Create a new project in Linear

linear_updateProjectC

Update an existing project in Linear

linear_addIssueToProjectC

Add an existing issue to a project

linear_getProjectIssuesB

Get all issues associated with a project

linear_getCyclesC

Get a list of all cycles

linear_getActiveCycleB

Get the currently active cycle for a team

linear_addIssueToCycleC

Add an issue to a cycle

linear_getIssuesC

Get a list of recent issues from Linear

linear_getIssueByIdA

Get a specific issue by ID or identifier (e.g., ABC-123)

linear_searchIssuesB

Search for issues with various filters

linear_createIssueC

Create a new issue in Linear

linear_updateIssueC

Update an existing issue in Linear

linear_createCommentC

Add a comment to an issue in Linear

linear_addIssueLabelB

Add a label to an issue in Linear

linear_removeIssueLabelC

Remove a label from an issue in Linear

linear_assignIssueB

Assign an issue to a user

linear_subscribeToIssueC

Subscribe to issue updates

linear_convertIssueToSubtaskC

Convert an issue to a subtask

linear_createIssueRelationA

Create relations between issues (blocks, is blocked by, etc.)

linear_archiveIssueC

Archive an issue

linear_setIssuePriorityC

Set the priority of an issue

linear_transferIssueB

Transfer an issue to another team

linear_duplicateIssueC

Duplicate an issue

linear_getIssueHistoryB

Get the history of changes made to an issue

linear_getCommentsC

Get all comments for an issue

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 32 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific resources and actions in Linear, such as linear_addIssueLabel vs. linear_removeIssueLabel or linear_getIssueById vs. linear_searchIssues. There is no ambiguity or overlap that would cause misselection, as each tool name precisely indicates its function.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with the 'linear_' prefix, such as linear_createIssue, linear_getIssues, and linear_updateIssue. The naming is uniform throughout, using snake_case and clear action verbs, making it highly predictable and readable.

Tool Count3/5

With 32 tools, the count is borderline high for a project management server, as it may feel heavy and complex for agents to navigate. While it covers many operations, a more streamlined set of 15-25 tools might be more appropriate for the scope without sacrificing functionality.

Completeness5/5

The tool surface provides comprehensive CRUD and lifecycle coverage for Linear's domain, including issue management (create, update, archive, duplicate), project handling, user and team operations, and advanced features like relations and subscriptions. There are no obvious gaps, and agents can perform full workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues