Linear Automation via Rube MCP
Automate Linear operations through Composio's Linear toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/linear
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 |
Powered by Composio
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**Toolkit docs**: [composio.dev/toolkits/linear](https://composio.dev/toolkits/linear)
11
12## Prerequisites
13
14- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
15- Active Linear connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`
16- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
17
18## Setup
19
20**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.
21
22
231. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
242. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `linear`
253. If connection is not ACTIVE, follow the returned auth link to complete Linear OAuth
264. Confirm connection status shows ACTIVE before running any workflows
27
28## Core Workflows
29
30### 1. Manage Issues
31
32**When to use**: User wants to create, search, update, or list Linear issues
33
34**Tool sequence**:
351. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team IDs [Prerequisite]
362. `LINEAR_LIST_LINEAR_STATES` - Get workflow states for a team [Prerequisite]
373. `LINEAR_CREATE_LINEAR_ISSUE` - Create a new issue [Optional]
384. `LINEAR_SEARCH_ISSUES` / `LINEAR_LIST_LINEAR_ISSUES` - Find issues [Optional]
395. `LINEAR_GET_LINEAR_ISSUE` - Get issue details [Optional]
406. `LINEAR_UPDATE_ISSUE` - Update issue properties [Optional]
41
42**Key parameters**:
43- `team_id`: Team ID (required for creation)
44- `title`: Issue title
45- `description`: Issue description (Markdown supported)
46- `state_id`: Workflow state ID
47- `assignee_id`: Assignee user ID
48- `priority`: 0 (none), 1 (urgent), 2 (high), 3 (medium), 4 (low)
49- `label_ids`: Array of label IDs
50
51**Pitfalls**:
52- Team ID is required when creating issues; use GET_ALL_LINEAR_TEAMS first
53- State IDs are team-specific; use LIST_LINEAR_STATES with the correct team
54- Priority uses integer values 0-4, not string names
55
56### 2. Manage Projects
57
58**When to use**: User wants to create or update Linear projects
59
60**Tool sequence**:
611. `LINEAR_LIST_LINEAR_PROJECTS` - List existing projects [Optional]
622. `LINEAR_CREATE_LINEAR_PROJECT` - Create a new project [Optional]
633. `LINEAR_UPDATE_LINEAR_PROJECT` - Update project details [Optional]
64
65**Key parameters**:
66- `name`: Project name
67- `description`: Project description
68- `team_ids`: Array of team IDs associated with the project
69- `state`: Project state (e.g., 'planned', 'started', 'completed')
70
71**Pitfalls**:
72- Projects span teams; they can be associated with multiple teams
73
74### 3. Manage Cycles
75
76**When to use**: User wants to work with Linear cycles (sprints)
77
78**Tool sequence**:
791. `LINEAR_GET_ALL_LINEAR_TEAMS` - Get team ID [Prerequisite]
802. `LINEAR_GET_CYCLES_BY_TEAM_ID` / `LINEAR_LIST_LINEAR_CYCLES` - List cycles [Required]
81
82**Key parameters**:
83- `team_id`: Team ID for cycle operations
84- `number`: Cycle number
85
86**Pitfalls**:
87- Cycles are team-specific; always scope by team_id
88
89### 4. Manage Labels and Comments
90
91**When to use**: User wants to create labels or comment on issues
92
93**Tool sequence**:
941. `LINEAR_CREATE_LINEAR_LABEL` - Create a new label [Optional]
952. `LINEAR_CREATE_LINEAR_COMMENT` - Comment on an issue [Optional]
963. `LINEAR_UPDATE_LINEAR_COMMENT` - Edit a comment [Optional]
97
98**Key parameters**:
99- `name`: Label name
100- `color`: Label color (hex)
101- `issue_id`: Issue ID for comments
102- `body`: Comment body (Markdown)
103
104**Pitfalls**:
105- Labels can be team-scoped or workspace-scoped
106- Comment body supports Markdown formatting
107
108### 5. Custom GraphQL Queries
109
110**When to use**: User needs advanced queries not covered by standard tools
111
112**Tool sequence**:
1131. `LINEAR_RUN_QUERY_OR_MUTATION` - Execute custom GraphQL [Required]
114
115**Key parameters**:
116- `query`: GraphQL query or mutation string
117- `variables`: Variables for the query
118
119**Pitfalls**:
120- Requires knowledge of Linear's GraphQL schema
121- Rate limits apply to GraphQL queries
122
123## Common Patterns
124
125### ID Resolution
126
127**Team name -> Team ID**:
128```
1291. Call LINEAR_GET_ALL_LINEAR_TEAMS
1302. Find team by name in response
1313. Extract id field
132```
133
134**State name -> State ID**:
135```
1361. Call LINEAR_LIST_LINEAR_STATES with team_id
1372. Find state by name
1383. Extract id field
139```
140
141### Pagination
142
143- Linear tools return paginated results
144- Check for pagination cursors in responses
145- Pass cursor to next request for additional pages
146
147## Known Pitfalls
148
149**Team Scoping**:
150- Issues, states, and cycles are team-specific
151- Always resolve team_id before creating issues
152
153**Priority Values**:
154- 0 = No priority, 1 = Urgent, 2 = High, 3 = Medium, 4 = Low
155- Use integer values, not string names
156
157## Quick Reference
158
159| Task | Tool Slug | Key Params |
160|------|-----------|------------|
161| List teams | LINEAR_GET_ALL_LINEAR_TEAMS | (none) |
162| Create issue | LINEAR_CREATE_LINEAR_ISSUE | team_id, title, description |
163| Search issues | LINEAR_SEARCH_ISSUES | query |
164| List issues | LINEAR_LIST_LINEAR_ISSUES | team_id, filters |
165| Get issue | LINEAR_GET_LINEAR_ISSUE | issue_id |
166| Update issue | LINEAR_UPDATE_ISSUE | issue_id, fields |
167| List states | LINEAR_LIST_LINEAR_STATES | team_id |
168| List projects | LINEAR_LIST_LINEAR_PROJECTS | (none) |
169| Create project | LINEAR_CREATE_LINEAR_PROJECT | name, team_ids |
170| Update project | LINEAR_UPDATE_LINEAR_PROJECT | project_id, fields |
171| List cycles | LINEAR_LIST_LINEAR_CYCLES | team_id |
172| Get cycles | LINEAR_GET_CYCLES_BY_TEAM_ID | team_id |
173| Create label | LINEAR_CREATE_LINEAR_LABEL | name, color |
174| Create comment | LINEAR_CREATE_LINEAR_COMMENT | issue_id, body |
175| Update comment | LINEAR_UPDATE_LINEAR_COMMENT | comment_id, body |
176| List users | LINEAR_LIST_LINEAR_USERS | (none) |
177| Current user | LINEAR_GET_CURRENT_USER | (none) |
178| Run GraphQL | LINEAR_RUN_QUERY_OR_MUTATION | query, variables |
179
180---
181*Powered by [Composio](https://composio.dev)*
majiayu000