Skip to main content
Glama
vinayak-mehta

Linear MCP Server

by vinayak-mehta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LINEAR_API_KEYYesYour Linear API key (create at https://linear.app/settings/account/security)

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
linear_create_issueB

Create a new Linear issue.

Args:
    title: Issue title
    team_id: Team ID to create issue in
    description: Issue description (markdown supported)
    priority: Priority level (1=urgent, 4=low)
    status: Initial status name
linear_update_issueB

Update an existing Linear issue.

Args:
    id: Issue ID to update
    title: New title
    description: New description
    priority: New priority (1=urgent, 4=low)
    status: New status name
linear_search_issuesB

Search issues with flexible filtering.

Args:
    query: Text to search in title/description
    team_id: Filter by team
    status: Filter by status
    assignee_id: Filter by assignee
    labels: Filter by labels
    priority: Filter by priority
    estimate: Filter by estimate points
    include_archived: Include archived issues
    limit: Max results (default: 10)
linear_get_user_issuesB

Get issues assigned to a user.

Args:
    user_id: User ID (omit for authenticated user)
    include_archived: Include archived issues
    limit: Max results (default: 50)
linear_add_commentB

Add a comment to an issue.

Args:
    issue_id: Issue ID to comment on
    body: Comment text (markdown supported)
    create_as_user: Custom username
    display_icon_url: Custom avatar URL

Prompts

Interactive templates invoked by user choice

NameDescription
defaultGet the default prompt for the Linear MCP server.

Resources

Contextual data attached and managed by the client

NameDescription
get_organizationGet the Linear organization. Returns: Organization details
get_viewerGet the authenticated user (viewer). Returns: User details
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: add_comment, create_issue, get_user_issues, search_issues, and update_issue target specific operations with no overlap. The descriptions reinforce these distinctions, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent 'linear_verb_noun' pattern (e.g., linear_add_comment, linear_create_issue). This predictable naming scheme enhances readability and agent usability without any deviations.

Tool Count4/5

With 5 tools, the count is reasonable for a Linear issue management server, covering core operations. It feels slightly thin but not inadequate, as key functions like create, read, update, and search are present.

Completeness4/5

The toolset covers essential CRUD operations for Linear issues (create, get, update, comment) and includes search functionality. Minor gaps exist, such as no delete_issue or list_teams tools, but agents can manage core workflows effectively.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources