claude.ai Linear MCP: save_status_update type="project" returns error despite schema declaring support
Summary
The claude.ai Linear MCP server declares type: "project" as a valid enum value in the save_status_update schema, but calling it with type: "project" returns an error — even when the Linear workspace has Project Updates enabled.
Steps to reproduce
- Enable Project Updates in a Linear workspace (Settings → Features → Project Updates)
- Call
save_status_updatewithtype: "project"and a valid project name/ID/slug - Observe the error
Error returned
Error: Project status updates are not enabled for this workspace. Pass `type: "initiative"` to manage initiative status updates instead.
The same error is returned by get_status_updates(type="project", ...).
Expected behavior
Both save_status_update and get_status_updates should work with type: "project" when the workspace has Project Updates enabled, consistent with what the schema declares.
Environment
- MCP server:
claude.ai Linear - Linear workspace: Project Updates feature confirmed enabled (weekly UI prompts for project updates are active)
- Verified: the constraint is connector-side, not a workspace setting
Impact
type: "project" and type: "initiative" are both declared as valid enum values in the MCP schema. The schema mismatch causes unexpected failures for users who follow the schema to post project-level status updates.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗