Linear MCP (multi-workspace, PAT auth)
PYPI · ADELAIDASOFIA-LINEAR-MCP · 2 COMPONENTS · SCANNED SEP 16
Multi-workspace Linear MCP — PAT auth, 57 tools + 3 prompts, substrate enforcement, drop-in.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 114 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3949 tokens (~69/item across 57 items; 57 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_webhook" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Linear MCP (multi-workspace, PAT auth) server?
Linear MCP (multi-workspace, PAT auth) runs locally as a PyPI package, launched with uvx adelaidasofia-linear-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · adelaidasofia-linear-mcp
claude mcp add adelaidasofia-linear-mcp -- uvx adelaidasofia-linear-mcp
{
"mcpServers": {
"adelaidasofia-linear-mcp": {
"command": "uvx",
"args": [
"adelaidasofia-linear-mcp"
]
}
}
} {
"servers": {
"adelaidasofia-linear-mcp": {
"command": "uvx",
"args": [
"adelaidasofia-linear-mcp"
]
}
}
} codex mcp add adelaidasofia-linear-mcp -- uvx adelaidasofia-linear-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"adelaidasofia-linear-mcp": {
"type": "local",
"command": [
"uvx",
"adelaidasofia-linear-mcp"
],
"enabled": true
}
}
} openclaw mcp add adelaidasofia-linear-mcp --command uvx --arg adelaidasofia-linear-mcp
mcp_servers:
adelaidasofia-linear-mcp:
command: "uvx"
args: ["adelaidasofia-linear-mcp"] {
"McpServers": {
"adelaidasofia-linear-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"adelaidasofia-linear-mcp"
]
}
}
} assistant mcp add adelaidasofia-linear-mcp -t stdio -c uvx -a adelaidasofia-linear-mcp
{
"mcpServers": {
"adelaidasofia-linear-mcp": {
"command": "uvx",
"args": [
"adelaidasofia-linear-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 −3
- Stability: pass → 0.80 functional
- 4 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Sept 2026 · Analysed pypi/adelaidasofia-linear-mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
archive_notification Archive Notification ~31
Archive a notification (removes from inbox; reversible).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
attachments_for_url Attachments For Url ~61
Reverse lookup: every attachment record across the workspace pointing at this URL. Useful to find which issue references a given Slack thread / PR / external doc.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | – | – |
| url | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
bulk_save_issues Bulk Save Issues ~250
Apply the same update to multiple issues in one round-trip. `ids` is a list of issue UUIDs. Every other arg is an optional field to set on all of them (skip args you don't want to change). Linear's `issueBatchUpdate` mutation does the work server-side — way faster than N separate `save_issue` calls for bulk ops like "mark these 50 as Done" or "reassign these to me." `auth_phrase` (REQUIRED, v0.3) must be one of: "go", "yes do it", "confirmed", "execute", "go cancel", "go update". Without this explicit confirmation a single hallucinated arg could mass-modify pre-existing shared workspace data — surface the requirement to the operator and capture their explicit phrase before calling this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | – | – | – |
| auth_phrase | string | yes | – |
| cycle_id | – | – | – |
| due_date | – | – | – |
| estimate | – | – | – |
| ids | array | yes | – |
| label_ids | – | – | – |
| priority | – | – | – |
| project_id | – | – | – |
| state_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_agent_session_on_comment Create Agent Session On Comment ~50
Open an agent session attached to a comment (typically a @mention of the agent app user).
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | – |
| external_url | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_agent_session_on_issue Create Agent Session On Issue ~102
Open an agent session attached to an issue. `session_type` is one of `comment` (the agent posts a comment as its output) or `commentThread` (the agent threads under existing comments). `external_url` lets the agent surface a link back to its own dashboard / run log.
| Name | Type | Req | Description |
|---|---|---|---|
| external_url | – | – | – |
| issue_id | string | yes | – |
| session_type | string | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_issue_label Create Issue Label ~103
Create a new issue label. `team_id` makes a team-scoped label. Omit for workspace-scoped. `color` is a 7-char hex (`#RRGGBB`). `parent_id` nests this label under another (Linear supports two-level label hierarchies).
| Name | Type | Req | Description |
|---|---|---|---|
| color | – | – | – |
| description | – | – | – |
| name | string | yes | – |
| parent_id | – | – | – |
| team_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_issue_relation Create Issue Relation ~94
Create a relation between two issues. `type` must be one of: `blocks` (issue blocks related_issue), `duplicate` (issue duplicates related_issue), or `related` (no directionality). Linear automatically creates the inverse relation visible on the other issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| related_issue_id | string | yes | – |
| type | string | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_webhook Create Webhook ~165
Create a webhook subscription. `url` is your HTTPS receiver. `resource_types` defaults to `["Issue", "Comment", "IssueLabel"]` if omitted — adjust as needed (full list at linear.app/developers/webhooks). `team_id` scopes to one team; `all_public_teams=True` subscribes to every public team in the org. `secret` is your HMAC signing secret — Linear adds it to the `Linear-Signature` header on every event.
| Name | Type | Req | Description |
|---|---|---|---|
| all_public_teams | boolean | – | – |
| enabled | boolean | – | – |
| label | – | – | – |
| resource_types | – | – | – |
| secret | – | – | – |
| team_id | – | – | – |
| url | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_attachment Delete Attachment ~82
Delete an attachment. Destructive — uses draft+confirm. Two-call flow identical to `delete_webhook`. The first call returns a draft_id + preview of the attachment that will be removed; the second call (with `confirm_draft_id`) commits.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_draft_id | – | – | – |
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_issue_relation Delete Issue Relation ~35
Delete an issue relation by ID. Non-destructive (no cascade).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_webhook Delete Webhook ~127
Delete a webhook. Destructive — uses draft+confirm. Two-call flow: 1. `delete_webhook(id=...)` returns a `draft_id` plus a preview of which webhook is about to go away. 2. `delete_webhook(id=..., confirm_draft_id=<draft_id>)` actually issues `webhookDelete` against Linear. Drafts expire after 1 hour (override with `LINEAR_MCP_DRAFT_TTL_SECONDS`).
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_draft_id | – | – | – |
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_agent_session Get Agent Session ~28
Get an agent session by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_attachment Get Attachment ~26
Get one attachment by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_document Get Document ~26
Get a document by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_initiative Get Initiative ~28
Get an initiative by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_issue Get Issue ~62
Get a single issue. `id` accepts either the UUID or the human identifier (e.g. `ONDE-123`). When given an identifier, the tool resolves it through a one-shot search.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_issue_status Get Issue Status ~61
Return the current workflow state for one issue (id or identifier). Convenience tool: the existing get_issue already returns state, but this is the minimal-fields variant for status-driven automations.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_milestone Get Milestone ~29
Get a project milestone by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_notification Get Notification ~26
Get one notification by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_project Get Project ~27
Get a Linear project by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_team Get Team ~33
Get a Linear team by its UUID. Includes workflow states inline.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_user Get User ~57
Get a Linear user by ID. Pass `me` to look up the PAT owner. For `me`, the server resolves it via the viewer query and substitutes the resolved id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_webhook Get Webhook ~27
Get a webhook by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
healthcheck Healthcheck ~71
Verify PAT validity for each workspace + report draft store + audit log path. For each workspace, calls the `viewer` query. Returns user info + the organization the PAT is scoped to. A failure means the PAT has been revoked or rotated and needs re-generation at linear.app/settings/account/security.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
link_url_to_issue Link Url To Issue ~85
Attach an arbitrary URL to an issue. Linear renders the link in the issue sidebar. Pass `title` and `icon_url` to customize the display; otherwise Linear fetches OpenGraph metadata from the URL.
| Name | Type | Req | Description |
|---|---|---|---|
| icon_url | – | – | – |
| issue_id | string | yes | – |
| title | – | – | – |
| url | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_agent_sessions List Agent Sessions ~45
List agent sessions. `issue_id` scopes to one issue.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| issue_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_attachments List Attachments ~40
List attachments on one issue.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| issue_id | string | yes | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_comments List Comments ~51
List comments. Scope by `issue_id` or `project_id`.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| issue_id | – | – | – |
| project_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_cycles List Cycles ~58
List cycles, optionally scoped to one team. `team_id` is the team UUID. Omit to list cycles across every team.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| team_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_documents List Documents ~31
List documents in the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_initiatives List Initiatives ~49
List initiatives in the workspace. Initiatives are Linear's top-level org-wide goals that contain multiple projects.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_issue_labels List Issue Labels ~50
List issue labels. `team_id` scopes to one team; omit for org-wide.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| team_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_issue_relations List Issue Relations ~48
List issue relations. `issue_id` filters to relations involving one issue.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| issue_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_issue_statuses List Issue Statuses ~65
List workflow states (issue statuses) per team. `team_id` scopes results to one team. Omit to list every workflow state across the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| team_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_issues List Issues ~171
List issues with common filters. `assignee_id` accepts a user UUID or the literal `me`. `state_type` accepts one of: backlog, unstarted, started, completed, canceled, triage. `query` does a full-text search across title + description. `filter` lets you pass a raw Linear IssueFilter for cases the convenience args don't cover. `order_by` is `updatedAt` (default) or `createdAt`.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| assignee_id | – | – | – |
| filter | – | – | – |
| first | integer | – | – |
| order_by | string | – | – |
| project_id | – | – | – |
| query | – | – | – |
| state_name | – | – | – |
| state_type | – | – | – |
| team_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_milestones List Milestones ~46
List project milestones. `project_id` scopes to one project.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| project_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_notifications List Notifications ~80
List notifications in the viewer's inbox. `unread_only=True` restricts to notifications with no `readAt`. Nodes carry `__typename` (IssueNotification, ProjectNotification, etc.) so an agent can branch on category.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| unread_only | boolean | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_projects List Projects ~80
List projects. `team_id` scopes to projects involving one team. `state` filters by project state (one of: backlog, planned, started, paused, completed, canceled). Omit for all.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| state | – | – | – |
| team_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_teams List Teams ~76
List teams in a Linear workspace. `workspace` selects which configured PAT to use (defaults to primary). `first` is the page size (max 250); `after` is the cursor from a previous response's pageInfo.endCursor.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_users List Users ~66
List users in a Linear workspace. `include_disabled` flips the Linear `includeDisabled` filter so you can see members who have been removed from the org.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| include_disabled | boolean | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_webhooks List Webhooks ~34
List webhooks configured for the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| after | – | – | – |
| first | integer | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_workspaces List Workspaces ~65
List configured Linear workspaces with PAT prefix + primary status. Returns a dict with `workspaces` (list of redacted profiles), `primary` (alias of the default workspace), and `errors` (config errors found at load time). Tokens never appear in the response.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
mark_all_notifications_read Mark All Notifications Read ~52
Mark every notification in the inbox as read. `category` optionally scopes to one notification category (e.g. `triageResponsibility`, `assigned`).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
mark_notification_read Mark Notification Read ~42
Mark a notification read (or unread by passing `read=False`).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| read | boolean | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
notifications_unread_count Notifications Unread Count ~25
Return the count of unread notifications in the inbox.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
save_comment Save Comment ~92
Create or update a comment. Pass `id` to edit an existing comment (only `body` is updateable). Creating requires `body` and either `issue_id` or `project_id`. `parent_id` threads the comment as a reply.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| id | – | – | – |
| issue_id | – | – | – |
| parent_id | – | – | – |
| project_id | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
save_document Save Document ~95
Create or update a document. Pass `id` to update. Creating requires `title` and one of `project_id` or `initiative_id` (documents attach to a project or initiative in Linear's model).
| Name | Type | Req | Description |
|---|---|---|---|
| color | – | – | – |
| content | – | – | – |
| icon | – | – | – |
| id | – | – | – |
| initiative_id | – | – | – |
| project_id | – | – | – |
| title | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
save_initiative Save Initiative ~104
Create or update an initiative. Pass `id` to update; omit to create. Status is one of `Planned`, `Active`, `Completed` (string, not enum) per Linear's API.
| Name | Type | Req | Description |
|---|---|---|---|
| color | – | – | – |
| content | – | – | – |
| description | – | – | – |
| icon | – | – | – |
| id | – | – | – |
| name | – | – | – |
| owner_id | – | – | – |
| status | – | – | – |
| target_date | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
save_issue Save Issue ~165
Create or update an issue. Pass `id` to update. Creating requires `title` and `team_id`. `assignee_id` accepts a UUID or `me`. `priority` is 0-4 (0=none, 1=urgent, 2=high, 3=medium, 4=low).
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | – | – | – |
| cycle_id | – | – | – |
| description | – | – | – |
| due_date | – | – | – |
| estimate | – | – | – |
| id | – | – | – |
| label_ids | – | – | – |
| parent_id | – | – | – |
| priority | – | – | – |
| project_id | – | – | – |
| project_milestone_id | – | – | – |
| state_id | – | – | – |
| team_id | – | – | – |
| title | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
save_milestone Save Milestone ~72
Create or update a project milestone. Pass `id` to update. Creating requires `name` and `project_id`.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | – |
| id | – | – | – |
| name | – | – | – |
| project_id | – | – | – |
| sort_order | – | – | – |
| target_date | – | – | – |
| workspace | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Linear MCP (multi-workspace, PAT auth) server?
Linear MCP (multi-workspace, PAT auth) is listed in the public MCP registry as io.github.adelaidasofia/linear-mcp. Multi-workspace Linear MCP, PAT auth, 57 tools + 3 prompts, substrate enforcement, drop-in. This page covers its PyPI package (adelaidasofia-linear-mcp).
Is the Linear MCP (multi-workspace, PAT auth) server safe to use?
Linear MCP (multi-workspace, PAT auth) scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Linear MCP (multi-workspace, PAT auth) server expose?
Linear MCP (multi-workspace, PAT auth) exposes 57 tools: list_workspaces, healthcheck, list_teams, get_team, list_users, and 52 more. Their descriptions and schemas cost roughly 3,949 tokens of context every time the server is loaded.
Is the Linear MCP (multi-workspace, PAT auth) server still maintained?
Linear MCP (multi-workspace, PAT auth) is still listed as active in the MCP registry. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Linear MCP (multi-workspace, PAT auth) server under?
Linear MCP (multi-workspace, PAT auth) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.