How to connect Linear to Claude Cowork

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Linear logo
Claude Cowork logo
divider

Introduction

Cowork is Anthropic's AI agent for knowledge work. Think of it as Claude Code for everything else. It works autonomously with your computer, local files, and applications to accomplish complex tasks.

This guide walks you through the easiest and most secure way to connect your Linear account to Cowork via Composio Connect, enabling it to create a new bug for team Mobile, add a comment to issue LIN-123, list all cycles for the Design team, and more such actions on your behalf without compromising your account security.

Also integrate Linear with

Connecting Linear to Claude Cowork

1. Open Customize

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

2. Add the Composio MCP server

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

3. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Cowork

4. Connect your Linear account

Back in Cowork, ask the agent to connect to Linear or give it any Linear-related task.

For example, ask Cowork to:

  • "Create a new bug for team Mobile"
  • "Add a comment to issue LIN-123"
  • "List all cycles for the Design team"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Cowork, and your Linear account is ready to use.

What is Claude Cowork?

Claude Cowork is Anthropic's agent for general knowledge work. It can use your computer, files, and connected applications to complete longer-running tasks across your work tools.

With Composio Connect, Cowork can securely access apps like Linear through MCP without you sharing account credentials directly with the agent.

What is the Linear MCP server, and what's possible with it?

The Linear MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Linear account. It provides structured and secure access to your team's issues, projects, and workflows, so your agent can perform actions like creating issues, posting comments, managing attachments, organizing teams, and automating project tracking on your behalf.

  • Automated issue creation and management: Instantly create new Linear issues, update existing ones, or archive issues to keep your team’s backlog organized and up to date.
  • Commenting and collaboration: Post comments on issues, facilitate team discussions, and keep everyone in the loop without manual effort.
  • Attachment handling: Add or download attachments to and from issues, making it easy to share files or reference important documents right from Linear.
  • Team and cycle insights: Retrieve all teams, fetch cycles (sprints) by team ID, and get default issue parameters to help your agent contextualize and optimize planning activities.
  • Personalized workspace access: Identify the current user, fetch their profile information, and tailor actions or queries to individual team members for smarter automation.

Supported Tools & Triggers

Tools
Triggers
Create attachmentCreates a new attachment and associates it with a specific, existing Linear issue.
Add reaction to commentTool to add a reaction to an existing Linear comment.
Create a commentCreates a new comment on a specified Linear issue.
Create linear issueCreates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date.
Create issue relationCreate a relationship between two Linear issues using the issueRelationCreate mutation.
Create a labelCreates a new label in Linear for a specified team, used to categorize and organize issues.
Create ProjectCreates a new Linear project with specified name and team associations.
Create Project MilestoneTool to create a project milestone in Linear with a name and optional target date and sort order.
Create Project UpdateTool to create a project status update post for a Linear project.
Delete issueArchives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent.
Download issue attachmentsDownloads a specific attachment from a Linear issue; the `file_name` must include the correct file extension.
Get current userGets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may be a bot or service account rather than a human user.
Get cycles by team IDRetrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints).
Get create issue default paramsFetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.
Get Linear issueRetrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.
Get Linear projectRetrieves a single Linear project by its unique identifier.
List issue draftsTool to list issue drafts.
List issues by team IDTool to list all issues for a specific Linear team, scoped by team ID.
Get all cyclesRetrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied.
List Linear issuesLists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned.
Get labelsRetrieves labels from Linear.
List linear projectsRetrieves all projects from the Linear account.
List Linear statesRetrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow.
Get teamsRetrieves all teams with their members and projects.
List Linear usersLists all workspace users (not team-scoped) with their IDs, names, emails, and active status.
Remove label from Linear issueRemoves a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue.
Remove reaction from commentTool to remove a reaction on a comment.
Run Query or MutationExecute any GraphQL query or mutation against Linear's API.
Search Linear issuesSearch Linear issues using full-text search across identifier, title, and description.
Update issueUpdates an existing Linear issue using its `issue_id`; requires at least one other attribute for modification, and all provided entity IDs (for state, assignee, labels, etc.
Update a commentTool to update an existing Linear comment's body text.
Update ProjectTool to update an existing Linear project.

How to build Linear MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Linear MCP?

With a standalone Linear MCP server, the agents and LLMs can only access a fixed set of Linear tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Linear and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Cowork?

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Linear tools.

Can I manage the permissions and scopes for Linear while using Tool Router?

Yes, absolutely. You can configure which Linear scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Linear data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.