You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`linear_getProjects`| Get a list of projects from Linear | ✅ Implemented |
77
+
|`linear_getProjectById`| Get details of a specific project | ✅ Implemented |
77
78
|`linear_createProject`| Create a new project in Linear | ✅ Implemented |
78
79
79
80
### Milestone Tools
@@ -90,15 +91,21 @@ Linear exposes milestones as `ProjectMilestone` in the SDK/API. Archiving is imp
90
91
91
92
### Document Tools
92
93
93
-
Linear exposes workspaceand project docs as `Document` in the SDK/API.
94
+
Linear exposes workspace, project, initiative, team, issue, release, and cycle docs as `Document` in the API. Team home resource sections use a narrow GraphQL query so MCP responses include richer pinned document/link details than the generated SDK fragment.
|`linear_updateProject`| Update an existing project | ✅ Implemented |
164
-
|`linear_createProjectUpdate`| Create a new update for a project | ✅ Implemented |
165
-
|`linear_updateProjectUpdate`| Update an existing project update | ✅ Implemented |
166
-
|`linear_getProjectUpdates`| Get updates for a project | ✅ Implemented |
171
+
|`linear_updateProject`| Update an existing project, including status, dates, members, lead, icon, and color | ✅ Implemented |
172
+
|`linear_createProjectUpdate`| Create a new update for a project with diff controls and fields in the response | ✅ Implemented |
173
+
|`linear_updateProjectUpdate`| Update an existing project update with diff controls and fields in the response | ✅ Implemented |
174
+
|`linear_getProjectUpdateById`| Get a specific project update, including diff metadata | ✅ Implemented |
175
+
|`linear_getProjectUpdates`| Get updates for a project, including Linear diff metadata | ✅ Implemented |
176
+
|`linear_archiveProjectUpdate`| Archive a project update | ✅ Implemented |
177
+
|`linear_unarchiveProjectUpdate`| Restore an archived project update | ✅ Implemented |
178
+
|`linear_deleteProjectUpdate`| Delete a project update | ✅ Implemented |
167
179
|`linear_archiveProject`| Archive a project | ✅ Implemented |
168
180
|`linear_addIssueToProject`| Add an existing issue to a project | ✅ Implemented |
169
181
|`linear_removeIssueFromProject`| Remove an existing issue from a project | ✅ Implemented |
@@ -174,7 +186,7 @@ These are MCP-server observability helpers for tool-only clients.
174
186
175
187
### Release Management Tools
176
188
177
-
This batch uses raw GraphQL instead of the installed SDK because the current public release schema is available but the local `@linear/sdk` package does not expose first-class release models yet. It now covers both the release/read note flows and the release pipeline/stage admin mutations exposed in the public alpha schema.
189
+
Release and release pipeline tools use focused GraphQL where this server needs custom response shaping for release notes, pipeline stages, and admin mutations. The package now targets the current `@linear/sdk` baseline.
|`linear_getCustomers`| Get customers with optional filters | ✅ Implemented |
276
+
|`linear_getCustomerById`| Get details of a specific customer | ✅ Implemented |
277
+
|`linear_createCustomer`| Create a customer | ✅ Implemented |
278
+
|`linear_updateCustomer`| Update a customer | ✅ Implemented |
279
+
|`linear_deleteCustomer`| Delete a customer | ✅ Implemented |
280
+
|`linear_getCustomerNeeds`| Get customer needs with optional filters | ✅ Implemented |
281
+
|`linear_getCustomerNeedById`| Get details of a specific customer need | ✅ Implemented |
282
+
|`linear_createCustomerNeed`| Create a customer need linked to an issue or project | ✅ Implemented |
283
+
|`linear_createCustomerNeedFromAttachment`| Create a customer need from an attachment | ✅ Implemented |
284
+
|`linear_updateCustomerNeed`| Update a customer need | ✅ Implemented |
285
+
|`linear_archiveCustomerNeed`| Archive a customer need | ✅ Implemented |
286
+
|`linear_unarchiveCustomerNeed`| Restore an archived customer need | ✅ Implemented |
287
+
|`linear_deleteCustomerNeed`| Delete a customer need | ✅ Implemented |
288
+
|`linear_getCustomerStatuses`| Get customer statuses | ✅ Implemented |
289
+
|`linear_getCustomerTiers`| Get customer tiers | ✅ Implemented |
250
290
251
291
### Views and Filters
252
292
@@ -312,6 +352,17 @@ The following tools are recommended for future implementation based on the curre
312
352
313
353
Items that looked conceptually mismatched with the current SDK or too speculative for this repo have been removed or moved to lower-priority sections.
314
354
355
+
### Recent Linear Surfaces Without Stable Tool Parity
356
+
357
+
These were reviewed against the current SDK/changelog but are intentionally not exposed as MCP tools yet because they do not have a stable SDK-backed request/response shape in this repo.
358
+
359
+
| Surface | Current Status |
360
+
| ------- | -------------- |
361
+
| Linear Diffs review operations | Product feature is available in Linear, but review/diff mutations are not exposed as stable SDK primitives for this MCP surface |
362
+
| Shared Linear Agent skills / `AgentSkill` migration | GraphQL types exist, but this repo does not yet expose an SDK-backed skills management surface |
363
+
| Team resource section/pin writes | Team resource reads are implemented; section/pin creation and reordering remain SDK/schema-gap candidates |
364
+
| GraphQL subscriptions and realtime updates | Supported by Linear's API, but not a good fit for this server's current stateless request/response tool model |
365
+
315
366
### Comment Management
316
367
317
368
Comment CRUD is now covered.
@@ -352,6 +403,10 @@ Linear milestones currently appear to belong to a single project in the SDK. Rea
352
403
353
404
Team settings, memberships, and team label management are now covered.
354
405
406
+
### Customers and Customer Needs
407
+
408
+
Customer records, customer statuses/tiers, and customer needs linked to issues or projects are now covered.
409
+
355
410
### Custom Fields
356
411
357
412
The repo already supports custom field discovery and issue value reads/updates. Admin CRUD appears to require the same kind of schema-driven GraphQL work used by the existing custom field support.
0 commit comments