How to connect Linear MCP with VS Code

Trusted by teams at
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Linear logo
VS Code logo
divider

How to connect Linear MCP with VS Code

VS Code is the most popular code editor out there. With its recent AI makeover, it can do more than just help you write code. You can connect your applications to it and let LLMs automate many of the mundane tasks in your workflow.

In this guide, I will explain how to connect Linear with VS Code in the most secure and robust way possible via Composio.

Also integrate Linear with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Programmatic tool calling. Allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Integrate Linear MCP with VS Code

1. Install with one click

Click the button below to add Composio to VS Code. You will be prompted to authorize. This requires VS Code 1.99+ with GitHub Copilot.

+Install in VS Code

2. Or add manually

Open or create .vscode/mcp.json in your project root and add the following configuration:

bash
{
  "servers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

3. Authorize

Click the install button to authorize VS Code to connect to Composio. VS Code will detect OAuth and prompt you to sign in.

VS Code MCP server install screen for Composio

A browser window will open to authorize.

Composio authorization browser window

4. Authenticate Linear and start working

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

For example, ask it 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 to Linear.

That is it. Composio tools are now available in VS Code, and your Linear account is ready to use.

Supported Tools & Triggers

Tools
Triggers
Create linear attachmentCreates a new attachment and associates it with a specific, existing linear issue.
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 a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Get create issue default paramsFetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a labelCreates a new label in linear for a specified team, used to categorize and organize issues.
Delete issueArchives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Get all teamsRetrieves all teams from the linear workspace without requiring any parameters.
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.
Get cycles by team IDRetrieves all cycles for a specified linear team id; cycles are time-boxed work periods (like sprints) and the team id must correspond to an existing team.
Get Linear issueRetrieves an existing linear issue's comprehensive details, including title, description, attachments, and comments.
Get all cyclesRetrieves all cycles (time-boxed iterations for work) from the linear account; no filters are applied.
List Linear issuesLists non-archived linear issues; if project id is not specified, issues from all accessible projects are returned.
Get labels by teamRetrieves all labels associated with a given team id in linear; the team id must refer to an existing team.
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 teams by projectRetrieves all teams, including their members, and filters each team's associated projects by the provided 'project id'.
List Linear usersLists all users in the linear workspace 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.
Run Query or MutationWildcard action that executes any graphql query or mutation against the linear api.
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.

Way Forward

Now that Linear is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
  • Connect HubSpot or Salesforce to log customer context, update records, and draft follow-ups.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

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 VS Code?

Yes, you can. VS Code 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.