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 titledescription: Issue description (Markdown supported)state_id: Workflow state IDassignee_id: Assignee user IDpriority: 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 namedescription: Project descriptionteam_ids: Array of team IDs associated with the projectstate: 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 operationsnumber: 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 namecolor: Label color (hex)issue_id: Issue ID for commentsbody: 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 stringvariables: 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 |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
1---2name: linear-automation3description: Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.4---5
6# Linear Automation via Rube MCP
7
8Automate Linear operations through Composio's Linear toolkit via Rube MCP.
9
10## Prerequisites
11
12- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
13- Active Linear connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`
14- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
15
16## Setup
17
18**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.
19
20
211. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
222. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`
233. If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth
244. Confirm connection status shows ACTIVE before running any workflows
25
26## Core Workflows
27
28### 1. Manage Issues
29
30**When to use**: User wants to create, search, update, or list Linear issues
31
32**Tool sequence**:
331. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team IDs [Prerequisite]
342. `LINEAR_LIST_LINEAR_STATES` - Get workflow states for a team [Prerequisite]
353. `LINEAR_CREATE_LINEAR_ISSUE` - Create a new issue [Optional]
364. `LINEAR_SEARCH_ISSUES` / `LINEAR_LIST_LINEAR_ISSUES` - Find issues [Optional]
375. `LINEAR_GET_LINEAR_ISSUE` - Get issue details [Optional]
386. `LINEAR_UPDATE_ISSUE` - Update issue properties [Optional]
39
40**Key parameters**:
41- `team_id`: Team ID (required for creation)
42- `title`: Issue title
43- `description`: Issue description (Markdown supported)
44- `state_id`: Workflow state ID
45- `assignee_id`: Assignee user ID
46- `priority`: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)
47- `label_ids`: Array of label IDs
48
49**Pitfalls**:
50- Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first
51- State IDs are team-specific; use LIST_LINEAR_STATES with the correct team
52- Priority uses integer values 0-4, not string names
53
54### 2. Manage Projects
55
56**When to use**: User wants to create or update Linear projects
57
58**Tool sequence**:
591. `LINEAR_LIST_LINEAR_PROJECTS` - List existing projects [Optional]
602. `LINEAR_CREATE_LINEAR_PROJECT` - Create a new project [Optional]
613. `LINEAR_UPDATE_LINEAR_PROJECT` - Update project details [Optional]
62
63**Key parameters**:
64- `name`: Project name
65- `description`: Project description
66- `team_ids`: Array of team IDs associated with the project
67- `state`: Project state (e.g., 'planned', 'started', 'completed')
68
69**Pitfalls**:
70- Projects span teams; they can be associated with multiple teams
71
72### 3. Manage Cycles
73
74**When to use**: User wants to work with Linear cycles (sprints)
75
76**Tool sequence**:
771. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team ID [Prerequisite]
782. `LINEAR_GET_CYCLES_BY_TEAM_ID` / `LINEAR_LIST_LINEAR_CYCLES` - List cycles [Required]
79
80**Key parameters**:
81- `team_id`: Team ID for cycle operations
82- `number`: Cycle number
83
84**Pitfalls**:
85- Cycles are team-specific; always scope by team_id
86
87### 4. Manage Labels and Comments
88
89**When to use**: User wants to create labels or comment on issues
90
91**Tool sequence**:
921. `LINEAR_CREATE_LINEAR_LABEL` - Create a new label [Optional]
932. `LINEAR_CREATE_LINEAR_COMMENT` - Comment on an issue [Optional]
943. `LINEAR_UPDATE_LINEAR_COMMENT` - Edit a comment [Optional]
95
96**Key parameters**:
97- `name`: Label name
98- `color`: Label color (hex)
99- `issue_id`: Issue ID for comments
100- `body`: Comment body (Markdown)
101
102**Pitfalls**:
103- Labels can be team-scoped or workspace-scoped
104- Comment body supports Markdown formatting
105
106### 5. Custom GraphQL Queries
107
108**When to use**: User needs advanced queries not covered by standard tools
109
110**Tool sequence**:
1111. `LINEAR_RUN_QUERY_OR_MUTATION` - Execute custom GraphQL [Required]
112
113**Key parameters**:
114- `query`: GraphQL query or mutation string
115- `variables`: Variables for the query
116
117**Pitfalls**:
118- Requires knowledge of Linear's GraphQL schema
119- Rate limits apply to GraphQL queries
120
121## Common Patterns
122
123### ID Resolution
124
125**Team name -> Team ID**:
126```
1271. Call LINEAR_GET_ALL_LINEAR_TEAMS
1282. Find team by name in response
1293. Extract id field
130```
131
132**State name -> State ID**:
133```
1341. Call LINEAR_LIST_LINEAR_STATES with team_id
1352. Find state by name
1363. Extract id field
137```
138
139### Pagination
140
141- Linear tools return paginated results
142- Check for pagination cursors in responses
143- Pass cursor to next request for additional pages
144
145## Known Pitfalls
146
147**Team Scoping**:
148- Issues, states, and cycles are team-specific
149- Always resolve team_id before creating issues
150
151**Priority Values**:
152- 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low
153- Use integer values, not string names
154
155## Quick Reference
156
157| Task | Tool Slug | Key Params |
158|------|-----------|------------|
159| List teams | LINEAR_GET_ALL_LINEAR_TEAMS | (none) |
160| Create issue | LINEAR_CREATE_LINEAR_ISSUE | team_id, title, description |
161| Search issues | LINEAR_SEARCH_ISSUES | query |
162| List issues | LINEAR_LIST_LINEAR_ISSUES | team_id, filters |
163| Get issue | LINEAR_GET_LINEAR_ISSUE | issue_id |
164| Update issue | LINEAR_UPDATE_ISSUE | issue_id, fields |
165| List states | LINEAR_LIST_LINEAR_STATES | team_id |
166| List projects | LINEAR_LIST_LINEAR_PROJECTS | (none) |
167| Create project | LINEAR_CREATE_LINEAR_PROJECT | name, team_ids |
168| Update project | LINEAR_UPDATE_LINEAR_PROJECT | project_id, fields |
169| List cycles | LINEAR_LIST_LINEAR_CYCLES | team_id |
170| Get cycles | LINEAR_GET_CYCLES_BY_TEAM_ID | team_id |
171| Create label | LINEAR_CREATE_LINEAR_LABEL | name, color |
172| Create comment | LINEAR_CREATE_LINEAR_COMMENT | issue_id, body |
173| Update comment | LINEAR_UPDATE_LINEAR_COMMENT | comment_id, body |
174| List users | LINEAR_LIST_LINEAR_USERS | (none) |
175| Current user | LINEAR_GET_CURRENT_USER | (none) |
176| Run GraphQL | LINEAR_RUN_QUERY_OR_MUTATION | query, variables |
177
178## When to Use
179This skill is applicable to execute the workflow or actions described in the overview.
kursku