Linear: confirm workspace before reading or writing

Use Linear MCP for issues and project workflows, confirming team and scope before writes.

Skills

First confirm that Linear MCP is connected and OAuth grants access to the workspace. If it is not connected, the skill documents `codex mcp add linear --url https://mcp.linear.app/mcp`, enabling the remote MCP client, and `codex mcp login linear`; a successful login may require a Codex restart. Clarify the goal, team, project, priority, labels, cycle, and assignee before acting. Read lists and statuses through MCP first, then create or update records in a logical batch. This integration has real write access: it can create issues, change statuses, add comments, or create projects. State the scope and make bulk grouping reviewable. Stop writes when authentication or required data is unclear.

Permissions

Prerequisites

The user asks to read or manage Linear issues, projects, cycles, labels, or docs; confirm workspace, team, and scope.
Requires a connected Linear MCP server and OAuth access; clarify targets and fields before writes.

Permissions

The MCP can read a workspace and create or update external issues, projects, labels, and comments.
OAuth login or MCP configuration changes local connections; explain grouping for bulk writes and stay within the user’s scope.

Limitations

Do not infer team, assignee, cycle, or due date from vague language. On connection failures, address authentication and restart requirements before retrying writes.