linearlisted

# /linear — Linear through MCP Everything goes through the **`linear` MCP server**, hosted at `https://mcp.linear.app/mcp`. This skill issues no REST calls and has no curl fallback. Wiring, OAuth and permission tiers: [docs/mcp-servers.md](../../docs/mcp-servers.md). ## First, check the server is there Tools appear as `mcp__linear__<tool>`. If none are available, say so and stop — do not reach for `curl` or `api.linear.app`. Run `/mcp` to connect, or `claude mcp list` to see what is configured. ## When to Use - Triage: list unresolved issues, read `ENG-123`, check a cycle or project - User pastes `https://linear.app/<workspace>/issue/ENG-123/...` - Filing or updating an issue for something found during a session - Team, workflow-state, label, project or document lookup ## When NOT to Use - Webhooks or building a Linear OAuth app → needs your own HTTP server - Bulk import or migration → Linear's own importers are safer - Linear Asks in Slack → that is Slack's side ## Tool map Read: | You want | Tool | |---|---| | issues, filtered | `list_issues` | | one issue | `get_issue`, then `list_comments` for its thread | | workflow states | `list_issue_statuses` | | teams / users | `list_teams`, `list_users` | | projects | `list_projects`, `get_project` | | cycles | `list_cycles` | | labels | `list_issue_labels`, `list_project_labels` | | docs, milestones | `list_documents`, `get_document`, `list_milestones` | | Linear's own docs | `search_documentation` | Write — each of th