Use
COMPOSIOFOR YOU
Give Claude, Codex, or any harness secure access to 1700+ tools
CLI
One command to add tools and auth to your coding agent
Build
DEVELOPER PLATFORM
SDKs, tools, and auth for agents and backend apps
MCP GATEWAY
One managed MCP endpoint for all your tools and agents
ENTERPRISE
SSO, governance, and audit controls for deploying agents org-wide
Features
TRIGGERS
Start background agents from events across your connected apps
FIREWALLNEW
Blocks instructions hidden in tool results before your agent reads them
INSTANTNEW
Audio, video, search, browser and data tools, with no keys to manage
OPTIMIZATION
Lower cost per completed task with optimised tools and skills
FOR AGENTS
CLAUDE CODEX OPENCLAW CURSOR HERMES
BUILT FOR
OFFICE WORK SALES MARKETING PRODUCT & DESIGN CUSTOMER SUPPORT ENGINEERING HR & RECRUITING FINANCE & OPS E-COMMERCE CONTENT & MEDIA IT & SECURITY
ALL USE CASES
DOCS

How to integrate Linear MCP with Claude Agent SDK

Connect Claude Agent SDK to Linear MCP. Create a new bug for team mobile, add a comment to issue lin-123, and more using natural language, with authentication handled for you.

Get started for free Get a demo

Linear

Oauth2Api Key

Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.

47 Tools12 Triggers

Managed auth

Connect Linear without auth hassles

We manage OAuth, API keys, token refresh, and scopes — you just build.

Book a call

Explore the MCP Gateway

Introduction

This guide walks you through connecting Linear to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Linear agent that can create and update issues, manage projects and milestones, post comments, track cycles, and search issues across teams through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Linear account through Composio's Linear MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:

Get and set up your Claude/Anthropic and Composio API keys
Install the necessary dependencies
Initialize Composio and create a Tool Router session for Linear
Configure an AI agent that can use Linear as a tool
Run a live chat session where you can ask the agent to perform Linear operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

Native MCP Support: Built-in support for Model Context Protocol servers
Permission Modes: Control tool execution permissions
Streaming Responses: Real-time response streaming for interactive applications
Context Manager: Clean async context management for sessions

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 issues, projects, milestones, updates, comments, and teams, so your agent can search and update issues, manage projects, create milestones, publish project updates, and configure teams on your behalf.

Issue search and updates: Have your agent find issues by keywords, update their details, and remove labels that no longer apply.
Project planning: Let the agent create projects, adjust existing projects, and associate new projects with the right teams.
Milestone management: Direct your agent to create project milestones with clear names and optional target dates.
Project status updates: Instruct your agent to list, publish, and revise project updates so stakeholders stay informed.
Team and conversation management: Have your agent create or update teams, review workspace comments, and remove reactions from comments.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS

Prerequisites

Before starting, make sure you have:

Composio API Key and Claude/Anthropic API Key
Primary know-how of Claude Agents SDK
A Linear account
Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key

Go to the Anthropic Console and create an API key. You'll need credits to use the models.
Keep the API key safe.

Composio API Key

Log in to the Composio dashboard.
Navigate to your API settings and generate a new API key.
Store this key securely as you'll need it for authentication.

Install dependencies

npm install @anthropic-ai/claude-agent-sdk @composio/core dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

@composio/core provides Composio integration for Anthropic
@anthropic-ai/claude-agent-sdk is the core agent framework
dotenv/config loads environment variables

Set up environment variables

bash

COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

COMPOSIO_API_KEY authenticates with Composio
USER_ID identifies the user for session management
ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

dotenv.config();

What's happening:

We're importing all necessary libraries including the Claude Agent SDK and Composio
The dotenv.config() function loads environment variables from your .env file
This setup prepares the foundation for connecting Claude with Linear functionality

Create a Composio instance and Tool Router session

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });

  // Create Tool Router session for Linear
  const session = await composio.create(USER_ID, {
    toolkits: ['linear'],
  });
  const mcpUrl = session?.mcp.url;

What's happening:

The function checks for the required COMPOSIO_API_KEY environment variable
We're creating a Composio instance using our API key
The create method creates a Tool Router session for Linear
The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

const options: Options = {
  permissionMode: 'bypassPermissions',
  mcpServers: {
    composio: {
      type: 'http',
      url: mcpUrl,
      headers: { 'x-api-key': COMPOSIO_API_KEY }
    }
  },
  systemPrompt: 'You are a helpful assistant with access to Linear tools via Composio.',
  maxTurns: 10,
};

What's happening:

We're configuring the Claude Agent options with the MCP server URL
permissionMode: 'bypassPermissions' allows the agent to execute operations without asking for permission each time
The system prompt instructs the agent that it has access to Linear
maxTurns: 10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

What's happening:

The readline interface is created to handle user input and output
The query function is used to send the user's input to the agent
The chat loop continues until the user types 'exit' or 'quit'

Run the application

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

What's happening:

The chat function is the entry point for the application
The try-catch block is used to handle any errors that occur

Complete Code

Here's the complete code to get you started with Linear and Claude Agent SDK:

import 'dotenv/config';
import readline from 'node:readline';
import { Composio } from '@composio/core';
import { query, type Options } from "@anthropic-ai/claude-agent-sdk";

async function chat() {
  const { COMPOSIO_API_KEY, USER_ID } = process.env;
  if (!COMPOSIO_API_KEY || !USER_ID) {
    throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
  }

  const composio = new Composio({ apiKey: COMPOSIO_API_KEY });
  const session = await composio.create(USER_ID, {
    toolkits: ['linear']
  });
  const mcp_url = session?.mcp.url;

  const options: Options = {
    permissionMode: 'bypassPermissions',
    mcpServers: {
      composio: {
        type: 'http',
        url: mcp_url,
        headers: { 'x-api-key': COMPOSIO_API_KEY }
      }
    },
    systemPrompt: 'You are a helpful assistant with access to Linear tools via Composio.',
    maxTurns: 10,
  };

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
  });

  console.log('\nChat started. Type "exit" to quit.\n');

  let isProcessing = false;

  async function ask(prompt: string) {
    isProcessing = true;
    rl.pause();

    process.stdout.write('Claude is thinking...');
    const stream = query({ prompt, options });

    let firstChunk = true;
    for await (const msg of stream) {
      const content = (msg as any).message?.content || (msg as any).content;
      if (Array.isArray(content)) {
        for (const block of content) {
          if (block.type === 'text' && block.text) {
            if (firstChunk) {
              process.stdout.write('\r\x1b[K');
              process.stdout.write('Claude: ');
              firstChunk = false;
            }
            process.stdout.write(block.text);
          }
        }
      }
    }
    process.stdout.write('\n\n');

    isProcessing = false;
    rl.resume();
    rl.prompt();
  }

  rl.on('line', async (line) => {
    if (isProcessing) return;

    const input = line.trim();
    if (input === 'exit') {
      rl.close();
      process.exit(0);
    }
    if (input) await ask(input);
    else rl.prompt();
  });

  await ask('What can you help me with?');
}

try {
  await chat();
} catch (error) {
  console.error(error);
  process.exit(1);
}

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Linear through Composio's Tool Router.

Key features:

Native MCP support through Claude's agent framework
Streaming responses for real-time interaction
Permission bypass for smooth automated workflows

You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

TOOLS & TRIGGERS

Supported Tools and Triggers

Every Linear action and event your agent gets out of the box.

Archive issue

Archives an existing Linear issue by its UUID or shorthand identifier, removing it from active views while preserving its data for future reference.

Archive Project

Archives an existing Linear project by its UUID, removing it from active views.

Archive Project Update

Archives a project update in Linear, hiding it from the default view while preserving its data.

Create attachment

Creates a new attachment and associates it with a specific, existing Linear issue.

Add reaction to comment

Tool to add a reaction to an existing Linear comment.

Create a comment

Creates a new comment on a specified Linear issue.

Create linear issue

Creates an issue in a specified Linear team with a title and optional project, description, assignee, state, priority, cycle, due date, and other properties.

Create issue relation

Create a relationship between two Linear issues using the issueRelationCreate mutation.

Create a label

Creates a label for a specified Linear team, or returns an existing exact-name match found in the team's initial label results.

Create Project

Creates a new Linear project with specified name and team associations.

Create Project Milestone

Tool to create a project milestone in Linear with a name and optional target date and sort order.

Create Project Update

Tool to create a project status update post for a Linear project.

Create Team

Creates a new team in Linear with the specified name and key.

Delete issue

Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent.

Download issue files

Downloads a Linear Attachment record or a private upload embedded in issue/comment Markdown; `file_name` must include the correct extension.

Get a comment

Retrieves a single Linear comment by its unique ID.

Get current user

Gets the currently authenticated Linear user's ID, name, email, and other profile information.

Get cycles by team ID

Lists cycles for a specified Linear team ID, including progress, creation and end times, and history.

Get create issue default params

Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.

Get Linear issue

Retrieves a Linear issue by UUID or shorthand identifier, including its details, parent, cycle, attachments, comments and subscribers.

Get Linear project

Retrieves a single Linear project by its unique identifier.

Get Project Update

Retrieves a specific project update by its unique identifier.

List comments

Lists comments from Linear workspace accessible to the authenticated user.

List issue drafts

Lists the connected user's issue drafts for review or editing.

List issues by team ID

Tool to list all issues for a specific Linear team, scoped by team ID.

Get all cycles

Lists cycles across the Linear account without filters, including team IDs and scheduled end times.

List Linear issues

Lists non-archived Linear issues with optional project and assignee filters, returning a paginated issues array and page_info.

Get labels

Retrieves paginated Linear issue labels for a specified team or across the workspace.

List linear projects

Retrieves all projects from the Linear account.

List Linear states

Retrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow.

Get teams

Lists visible Linear teams with their members and project IDs, with pagination for teams but not nested members or projects.

List Linear users

Lists workspace users with IDs, names, emails, and active status.

List project updates

Retrieves all project updates from the Linear workspace.

Remove label from Linear issue

Removes a specified label from a Linear issue using the issue and label IDs, and returns the updated issue and labels.

Remove reaction from comment

Tool to remove a reaction on a comment.

Resolve comment

Marks a Linear comment as resolved.

Run Query or Mutation

Execute a Linear GraphQL query or mutation to retrieve or change accessible data.

Search Linear issues

Searches Linear issues by full-text query, with pagination and an option to include archived issues.

Unarchive Project Update

Unarchive a previously archived project update in Linear.

Unresolve a comment

Unresolves a previously resolved Linear comment, marking it as requiring attention again.

Update issue

Updates an existing Linear issue by ID, requiring at least one field to modify; supplied fields overwrite existing values and labels replace the label set.

Update a comment

Tool to update an existing Linear comment's body text.

Update Project

Tool to update an existing Linear project.

Update Project Update

Tool to update an existing Linear project update post.

Update Team

Updates an existing Linear team's settings, including its name, key, cycle settings, and workflow state configuration.

Validate credential

Validates the Linear API credentials by checking if the authentication token can successfully query the current user.

Who Am I

Return the identity (name, email) of the connected Linear account.

FRAMEWORKS

How to build Linear MCP Agent with another framework

Claude Code

Use Linear MCP with Claude Code

Cursor

Use Linear MCP with Cursor

ChatGPT

Use Linear MCP with ChatGPT

Claude Cowork

Use Linear MCP with Claude Cowork

Antigravity

Use Linear MCP with Antigravity

OpenAI Agents SDK

Use Linear MCP with OpenAI Agents SDK

Grok Bot

Use Linear MCP with Grok Bot

Muse

Use Linear MCP with Muse

Codex

Use Linear MCP with Codex

Kimi Code

Use Linear MCP with Kimi Code

Grok Build

Use Linear MCP with Grok Build

VS Code

Use Linear MCP with VS Code

OpenCode

Use Linear MCP with OpenCode

OpenClaw

Use Linear MCP with OpenClaw

Hermes

Use Linear MCP with Hermes

Atomic Agent

Use Linear MCP with Atomic Agent

CLI

Use Linear MCP with CLI

Google ADK

Use Linear MCP with Google ADK

LangChain

Use Linear MCP with LangChain

Vercel AI SDK

Use Linear MCP with Vercel AI SDK

Mastra AI

Use Linear MCP with Mastra AI

LlamaIndex

Use Linear MCP with LlamaIndex

CrewAI

Use Linear MCP with CrewAI

Pydantic AI

Use Linear MCP with Pydantic AI

AutoGen

Use Linear MCP with AutoGen

MORE TOOLKITS

Explore Other Toolkits

Toolkit marketplace

Google Sheets

Oauth2

Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.

Notion

Oauth2Api Key

Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.

Airtable

Oauth2Api Key

Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.

Asana

Oauth2

Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.

FAQ

Frequently asked questions

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.

Yes, you can. Claude Agent SDK 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.

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.

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.

Start with Linear.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Linear tool your agent needs.Free to start.

Start building

How to integrate Linear MCP with Claude Agent SDK

Connect Linear without auth hassles

Introduction

Also integrate Linear with

TL;DR

What is Claude Agent SDK?

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

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

How the Composio SDK works

Step-by-step Guide

Prerequisites

Getting API Keys for Claude/Anthropic and Composio

Install dependencies

Set up environment variables

Import dependencies

Create a Composio instance and Tool Router session

Configure Claude Agent with MCP

Create client and start chat loop

Run the application

Complete Code

Conclusion

Supported Tools and Triggers

How to build Linear MCP Agent with another framework

Claude Code

Cursor

ChatGPT

Claude Cowork

Antigravity

OpenAI Agents SDK

Grok Bot

Muse

Codex

Kimi Code

Grok Build

VS Code

OpenCode

OpenClaw

Hermes

Atomic Agent

CLI

Google ADK

LangChain

Vercel AI SDK

Mastra AI

LlamaIndex

CrewAI

Pydantic AI

AutoGen

Explore Other Toolkits

Google Sheets

Notion

Airtable

Asana

Frequently asked questions

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

Can I use Tool Router MCP with Claude Agent SDK?

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

How safe is my data with Composio Tool Router?

Start with Linear.It takes 30 seconds.