Linear

Linear

Linear work MUST use literal MCPorter server linear.

• Live schema MUST remain authoritative when inspected
• The catalog is a dated fallback snapshot

Required follow-up reads

Tool routes

This stable name index is the default discovery layer. Read only the matching catalog section when its signature or safety notes are needed.

Common reads

These complete recipes use known inputs and SHOULD be called directly:

mcporter call linear.list_issues assignee=me orderBy=updatedAt limit=5 --output json
mcporter call linear.get_issue id=ENG-42 --output json
mcporter call linear.list_projects query='<name>' limit=50 --output json
mcporter call linear.list_comments issueId=ENG-42 limit=50 --output json
mcporter call linear.list_teams query='<name>' limit=50 --output json
mcporter call linear.list_users query='<name-or-email>' limit=50 --output json

list_issues common inputs: limit?:number=50, orderBy?:createdAt|updatedAt=updatedAt, assignee?:string|null; assignee=me selects the current user. Priority values are 0=None, 1=Urgent, 2=High, 3=Medium, 4=Low.

--output json selects rendering, not a response contract. Inspect returned issue records defensively for requested fields; input-schema discovery cannot validate output fields.

Recovery

• Missing generated registry: MUST report the setup failure.
• NEVER add or substitute a registry.
• NEVER expose, copy, or log tokens

mcporter list linear --status --no-oauth --exit-code
mcporter list linear --brief
mcporter list linear.<tool> --schema

• Select the tool from the route index; search only its catalog section for an unknown signature

• If the needed capability is absent from the index, use brief live inventory

• Inputs absent from a common recipe or catalog signature: inspect targeted live schema

• Rejected inputs or tool-not-found errors: inspect targeted live schema, then retry once

• Every mutation: MUST inspect targeted live schema

• Live discovery failure: MAY use the relevant catalog entry and MUST disclose possible drift

• NEVER invent tools, arguments, or response fields

• Run status only after a connection or authentication failure

• Auth failure: MUST run mcporter auth linear, then recheck status

• Persistent 401/403: MUST report missing access. NEVER write

Calls

mcporter call linear.<tool> key=value --output json
mcporter call 'linear.<tool>(arg: "value")' --output json
mcporter call linear.<tool> --args '{"id":"ENG-42","labels":["Bug"]}' --output json
mcporter call linear.<tool> body=@comment.md --output json

• Simple scalars SHOULD use key=value
• Typed literals SHOULD use function syntax
• Structured or multiline values SHOULD use --args
• UTF-8 files SHOULD use key=@path; @@ means literal @
• MUST quote shell-sensitive values
• Image responses SHOULD use --save-images <directory>

Safety

• Before writes: MUST resolve target and inspect write schema
• MUST apply the smallest change, then re-read
• save_issue: omitted id creates; supplied id updates
• Creation MUST include title and team
• labels replaces all labels; omission preserves them
• Nullable fields clear only with explicit null
• NEVER combine mutually exclusive release fields
• New comments MUST include body and exactly one parent
• Replies MUST use parentId
• Uncertain timeout: MUST read/search before retrying
• Bulk/destructive writes MUST have intent, confirmation, targeted schema
• Validation errors: MUST correct payload against live schema
• NEVER drop rejected fields silently
• Paginated reads MUST use filters/cursors and disclose boundaries