How jerhadf/linear-mcp-server works
This deprecated server exposes Linear issue-tracking operations to an MCP client over stdio. An LLM client invokes tools or requests resources; the server dispatches those requests to a Linear API client and returns results. The README documents issue creation, updates, search, comments, team/user queries, and organization context. The implementation is concentrated in index.ts; excerpts show startup, rate limiting, and some resource dispatch, but not every tool handler, so documented but unsampled operation links cite the README.
Main entry points: index.ts Linear client
Components 13
MCP interface
- MCP server
index.ts - Tool dispatch
index.ts - Resource dispatch
index.ts
Issue operations
- Linear client
index.ts - Rate limiter
index.ts - Issue mutations
index.ts - Issue search
index.ts - Issue comments
index.ts
Linear context
- Assigned issues
index.ts - Team issues
index.ts - Organization context
index.ts
Other components
- LLM client
- Linear API
Connections 19
- LLM client → MCP server: sends requests
README.md - MCP server → Tool dispatch: dispatches tools
index.ts - MCP server → Resource dispatch: routes resources
index.ts - Tool dispatch → Issue mutations: invokes
README.md - Tool dispatch → Issue search: invokes
README.md - Tool dispatch → Issue comments: invokes
README.md - Tool dispatch → Assigned issues: invokes
index.ts - Resource dispatch → Assigned issues: requests
index.ts - Resource dispatch → Team issues: requests
index.ts - Resource dispatch → Organization context: requests
index.ts - Resource dispatch → Linear client: requests data
index.ts - Issue mutations → Linear client: uses
index.ts - Issue search → Linear client: uses
index.ts - Issue comments → Linear client: uses
index.ts - Assigned issues → Linear client: uses
index.ts - Team issues → Linear client: uses
index.ts - Organization context → Linear client: uses
index.ts - Linear client → Rate limiter: queues requests
index.ts - Linear client → Linear API: queries