Tiger Linear MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINEAR_API_KEY | Yes | Your Linear API key |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_issueA | Fetches the details of a specific issue by its key. |
| get_issuesA | Fetches issues filtered by user ID and/or project ID. |
| get_usersB | Fetches all users within the Linear organization. |
| get_projectsB | Fetches all projects within the Linear organization. |
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 4 tools
Each tool targets a distinct resource and granularity: single issue, list of issues, all users, and all projects. There is no overlap or ambiguity between singular and plural forms.
All tools follow the consistent 'get_<resource>' pattern, making the API intuitive and predictable. No mixed conventions or vague verbs.
Four tools is well within the ideal 3-15 range and each tool earns its place by covering the core read operations for issues, users, and projects. The count feels appropriate for a focused read-only server.
The tool surface is read-only only, with no create, update, or delete operations for issues or other resources. For a Linear server, there are also missing common resources like teams and cycles, leaving significant gaps for any agent needing to manage workflows.