name: linear-automation
description: "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas."
Linear Automation via Rube MCP
Automate Linear operations through Composio's Linear toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Linear connection via
RUBE_MANAGE_CONNECTIONS with toolkit linear
- Always call
RUBE_SEARCH_TOOLS first to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLS responds
- Call
RUBE_MANAGE_CONNECTIONS with toolkit linear
- If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Issues
When to use: User wants to create, search, update, or list Linear issues
Tool sequence:
LINEAR_GET_ALL_LINEAR_TEAMS - Get team IDs [Prerequisite]
LINEAR_LIST_LINEAR_STATES - Get workflow states for a team [Prerequisite]
LINEAR_CREATE_LINEAR_ISSUE - Create a new issue [Optional]
LINEAR_SEARCH_ISSUES / LINEAR_LIST_LINEAR_ISSUES - Find issues [Optional]
LINEAR_GET_LINEAR_ISSUE - Get issue details [Optional]
LINEAR_UPDATE_ISSUE - Update issue properties [Optional]
Key parameters:
team_id: Team ID (required for creation)
title: Issue title
description: Issue description (Markdown supported)
state_id: Workflow state ID
assignee_id: Assignee user ID
priority: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)
label_ids: Array of label IDs
Pitfalls:
- Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first
- State IDs are team-specific; use LIST_LINEAR_STATES with the correct team
- Priority uses integer values 0-4, not string names
2. Manage Projects
When to use: User wants to create or update Linear projects
Tool sequence:
LINEAR_LIST_LINEAR_PROJECTS - List existing projects [Optional]
LINEAR_CREATE_LINEAR_PROJECT - Create a new project [Optional]
LINEAR_UPDATE_LINEAR_PROJECT - Update project details [Optional]
Key parameters:
name: Project name
description: Project description
team_ids: Array of team IDs associated with the project
state: Project state (e.g., 'planned', 'started', 'completed')
Pitfalls:
- Projects span teams; they can be associated with multiple teams
3. Manage Cycles
When to use: User wants to work with Linear cycles (sprints)
Tool sequence:
LINEAR_GET_ALL_LINEAR_TEAMS - Get team ID [Prerequisite]
LINEAR_GET_CYCLES_BY_TEAM_ID / LINEAR_LIST_LINEAR_CYCLES - List cycles [Required]
Key parameters:
team_id: Team ID for cycle operations
number: Cycle number
Pitfalls:
- Cycles are team-specific; always scope by team_id
4. Manage Labels and Comments
When to use: User wants to create labels or comment on issues
Tool sequence:
LINEAR_CREATE_LINEAR_LABEL - Create a new label [Optional]
LINEAR_CREATE_LINEAR_COMMENT - Comment on an issue [Optional]
LINEAR_UPDATE_LINEAR_COMMENT - Edit a comment [Optional]
Key parameters:
name: Label name
color: Label color (hex)
issue_id: Issue ID for comments
body: Comment body (Markdown)
Pitfalls:
- Labels can be team-scoped or workspace-scoped
- Comment body supports Markdown formatting
5. Custom GraphQL Queries
When to use: User needs advanced queries not covered by standard tools
Tool sequence:
LINEAR_RUN_QUERY_OR_MUTATION - Execute custom GraphQL [Required]
Key parameters:
query: GraphQL query or mutation string
variables: Variables for the query
Pitfalls:
- Requires knowledge of Linear's GraphQL schema
- Rate limits apply to GraphQL queries
Common Patterns
ID Resolution
Team name -> Team ID:
1. Call LINEAR_GET_ALL_LINEAR_TEAMS
2. Find team by name in response
3. Extract id field
State name -> State ID:
1. Call LINEAR_LIST_LINEAR_STATES with team_id
2. Find state by name
3. Extract id field
Pagination
- Linear tools return paginated results
- Check for pagination cursors in responses
- Pass cursor to next request for additional pages
Known Pitfalls
Team Scoping:
- Issues, states, and cycles are team-specific
- Always resolve team_id before creating issues
Priority Values:
- 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low
- Use integer values, not string names
Quick Reference
| Task |
Tool Slug |
Key Params |
| List teams |
LINEAR_GET_ALL_LINEAR_TEAMS |
(none) |
| Create issue |
LINEAR_CREATE_LINEAR_ISSUE |
team_id, title, description |
| Search issues |
LINEAR_SEARCH_ISSUES |
query |
| List issues |
LINEAR_LIST_LINEAR_ISSUES |
team_id, filters |
| Get issue |
LINEAR_GET_LINEAR_ISSUE |
issue_id |
| Update issue |
LINEAR_UPDATE_ISSUE |
issue_id, fields |
| List states |
LINEAR_LIST_LINEAR_STATES |
team_id |
| List projects |
LINEAR_LIST_LINEAR_PROJECTS |
(none) |
| Create project |
LINEAR_CREATE_LINEAR_PROJECT |
name, team_ids |
| Update project |
LINEAR_UPDATE_LINEAR_PROJECT |
project_id, fields |
| List cycles |
LINEAR_LIST_LINEAR_CYCLES |
team_id |
| Get cycles |
LINEAR_GET_CYCLES_BY_TEAM_ID |
team_id |
| Create label |
LINEAR_CREATE_LINEAR_LABEL |
name, color |
| Create comment |
LINEAR_CREATE_LINEAR_COMMENT |
issue_id, body |
| Update comment |
LINEAR_UPDATE_LINEAR_COMMENT |
comment_id, body |
| List users |
LINEAR_LIST_LINEAR_USERS |
(none) |
| Current user |
LINEAR_GET_CURRENT_USER |
(none) |
| Run GraphQL |
LINEAR_RUN_QUERY_OR_MUTATION |
query, variables |
1---2name: linear-automation-33description: <!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->4---5<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->6---7name: linear-automation8description: "Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas."9---1011# Linear Automation via Rube MCP1213Automate Linear operations through Composio's Linear toolkit via Rube MCP.1415## Prerequisites1617- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)18- Active Linear connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`19- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas2021## Setup2223**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.2425261. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds272. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`283. If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth294. Confirm connection status shows ACTIVE before running any workflows3031## Core Workflows3233### 1. Manage Issues3435**When to use**: User wants to create, search, update, or list Linear issues3637**Tool sequence**:381. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team IDs [Prerequisite]392. `LINEAR_LIST_LINEAR_STATES` - Get workflow states for a team [Prerequisite]403. `LINEAR_CREATE_LINEAR_ISSUE` - Create a new issue [Optional]414. `LINEAR_SEARCH_ISSUES` / `LINEAR_LIST_LINEAR_ISSUES` - Find issues [Optional]425. `LINEAR_GET_LINEAR_ISSUE` - Get issue details [Optional]436. `LINEAR_UPDATE_ISSUE` - Update issue properties [Optional]4445**Key parameters**:46- `team_id`: Team ID (required for creation)47- `title`: Issue title48- `description`: Issue description (Markdown supported)49- `state_id`: Workflow state ID50- `assignee_id`: Assignee user ID51- `priority`: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)52- `label_ids`: Array of label IDs5354**Pitfalls**:55- Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first56- State IDs are team-specific; use LIST_LINEAR_STATES with the correct team57- Priority uses integer values 0-4, not string names5859### 2. Manage Projects6061**When to use**: User wants to create or update Linear projects6263**Tool sequence**:641. `LINEAR_LIST_LINEAR_PROJECTS` - List existing projects [Optional]652. `LINEAR_CREATE_LINEAR_PROJECT` - Create a new project [Optional]663. `LINEAR_UPDATE_LINEAR_PROJECT` - Update project details [Optional]6768**Key parameters**:69- `name`: Project name70- `description`: Project description71- `team_ids`: Array of team IDs associated with the project72- `state`: Project state (e.g., 'planned', 'started', 'completed')7374**Pitfalls**:75- Projects span teams; they can be associated with multiple teams7677### 3. Manage Cycles7879**When to use**: User wants to work with Linear cycles (sprints)8081**Tool sequence**:821. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team ID [Prerequisite]832. `LINEAR_GET_CYCLES_BY_TEAM_ID` / `LINEAR_LIST_LINEAR_CYCLES` - List cycles [Required]8485**Key parameters**:86- `team_id`: Team ID for cycle operations87- `number`: Cycle number8889**Pitfalls**:90- Cycles are team-specific; always scope by team_id9192### 4. Manage Labels and Comments9394**When to use**: User wants to create labels or comment on issues9596**Tool sequence**:971. `LINEAR_CREATE_LINEAR_LABEL` - Create a new label [Optional]982. `LINEAR_CREATE_LINEAR_COMMENT` - Comment on an issue [Optional]993. `LINEAR_UPDATE_LINEAR_COMMENT` - Edit a comment [Optional]100101**Key parameters**:102- `name`: Label name103- `color`: Label color (hex)104- `issue_id`: Issue ID for comments105- `body`: Comment body (Markdown)106107**Pitfalls**:108- Labels can be team-scoped or workspace-scoped109- Comment body supports Markdown formatting110111### 5. Custom GraphQL Queries112113**When to use**: User needs advanced queries not covered by standard tools114115**Tool sequence**:1161. `LINEAR_RUN_QUERY_OR_MUTATION` - Execute custom GraphQL [Required]117118**Key parameters**:119- `query`: GraphQL query or mutation string120- `variables`: Variables for the query121122**Pitfalls**:123- Requires knowledge of Linear's GraphQL schema124- Rate limits apply to GraphQL queries125126## Common Patterns127128### ID Resolution129130**Team name -> Team ID**:131```1321. Call LINEAR_GET_ALL_LINEAR_TEAMS1332. Find team by name in response1343. Extract id field135```136137**State name -> State ID**:138```1391. Call LINEAR_LIST_LINEAR_STATES with team_id1402. Find state by name1413. Extract id field142```143144### Pagination145146- Linear tools return paginated results147- Check for pagination cursors in responses148- Pass cursor to next request for additional pages149150## Known Pitfalls151152**Team Scoping**:153- Issues, states, and cycles are team-specific154- Always resolve team_id before creating issues155156**Priority Values**:157- 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low158- Use integer values, not string names159160## Quick Reference161162| Task | Tool Slug | Key Params |163|------|-----------|------------|164| List teams | LINEAR_GET_ALL_LINEAR_TEAMS | (none) |165| Create issue | LINEAR_CREATE_LINEAR_ISSUE | team_id, title, description |166| Search issues | LINEAR_SEARCH_ISSUES | query |167| List issues | LINEAR_LIST_LINEAR_ISSUES | team_id, filters |168| Get issue | LINEAR_GET_LINEAR_ISSUE | issue_id |169| Update issue | LINEAR_UPDATE_ISSUE | issue_id, fields |170| List states | LINEAR_LIST_LINEAR_STATES | team_id |171| List projects | LINEAR_LIST_LINEAR_PROJECTS | (none) |172| Create project | LINEAR_CREATE_LINEAR_PROJECT | name, team_ids |173| Update project | LINEAR_UPDATE_LINEAR_PROJECT | project_id, fields |174| List cycles | LINEAR_LIST_LINEAR_CYCLES | team_id |175| Get cycles | LINEAR_GET_CYCLES_BY_TEAM_ID | team_id |176| Create label | LINEAR_CREATE_LINEAR_LABEL | name, color |177| Create comment | LINEAR_CREATE_LINEAR_COMMENT | issue_id, body |178| Update comment | LINEAR_UPDATE_LINEAR_COMMENT | comment_id, body |179| List users | LINEAR_LIST_LINEAR_USERS | (none) |180| Current user | LINEAR_GET_CURRENT_USER | (none) |181| Run GraphQL | LINEAR_RUN_QUERY_OR_MUTATION | query, variables |182183<!-- Source: .faos/custom/skills/devops/linear-automation/SKILL.md -->