# How to integrate Linear MCP with Codex

```json
{
  "title": "How to integrate Linear MCP with Codex",
  "toolkit": "Linear",
  "toolkit_slug": "linear",
  "framework": "Codex",
  "framework_slug": "codex",
  "url": "https://composio.dev/toolkits/linear/framework/codex",
  "markdown_url": "https://composio.dev/toolkits/linear/framework/codex.md",
  "updated_at": "2026-10-12T13:38:40.902Z"
}
```

## Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Linear MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

## Also integrate Linear with

- [Claude Code](https://composio.dev/toolkits/linear/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/linear/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/linear/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/linear/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/linear/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/linear/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/linear/framework/claude-agents-sdk)
- [Grok Bot](https://composio.dev/toolkits/linear/framework/grok-bot)
- [Muse](https://composio.dev/toolkits/linear/framework/muse)
- [Kimi Code](https://composio.dev/toolkits/linear/framework/kimi)
- [Grok Build](https://composio.dev/toolkits/linear/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/linear/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/linear/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/linear/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/linear/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/linear/framework/atomic-agent)
- [CLI](https://composio.dev/toolkits/linear/framework/cli)
- [Google ADK](https://composio.dev/toolkits/linear/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/linear/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/linear/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/linear/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/linear/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/linear/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/linear/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/linear/framework/autogen)

## TL;DR

### Why use Composio?
Apart from a managed and hosted MCP server, you will get:
- CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
- Large tool responses: Handle them to minimise context rot.
- Dynamic just-in-time access to 20,000 tools across 1500+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

## Connect Linear to Codex

### How to install Linear MCP in Codex
### Run the setup command
Run this command in your terminal to add the Composio MCP server to Codex.

```bash
codex mcp add composio --url https://connect.composio.dev/mcp
```

## 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.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `LINEAR_ARCHIVE_ISSUE` | Archive issue | Archives an existing Linear issue by its ID, removing it from active views while preserving its data for future reference. Use this action when you need to remove an issue from active work without permanently deleting it — for example, when an issue is no longer relevant, was created by mistake, or has been superseded by another issue. Archiving is reversible via the unarchive mutation, unlike permanent deletion. This action is irreversible through the API once completed, though issues can be manually unarchived in the Linear UI or via the issueUnarchive mutation. |
| `LINEAR_ARCHIVE_PROJECT` | Archive Project | Archives an existing Linear project by its UUID, removing it from active views. Use this action when you need to mark a completed or obsolete project as archived. Archiving is reversible (projects can be unarchived later), but confirm the project name with the user before executing, especially in bulk operations. |
| `LINEAR_ARCHIVE_PROJECT_UPDATE` | Archive Project Update | Archives a project update in Linear, hiding it from the default view while preserving its data. Use this action when you need to clean up old or obsolete project status updates without permanently deleting them. Archived updates can be unarchived later if needed. This action is irreversible only in the sense that the project update will be hidden from active views until explicitly unarchived. |
| `LINEAR_CREATE_ATTACHMENT` | Create attachment | Creates a new attachment and associates it with a specific, existing Linear issue. |
| `LINEAR_CREATE_COMMENT_REACTION` | Add reaction to comment | Tool to add a reaction to an existing Linear comment. Use when you want to programmatically react to a comment on an issue. |
| `LINEAR_CREATE_LINEAR_COMMENT` | Create a comment | Creates a new comment on a specified Linear issue. This action modifies shared workspace data and is not reversible — confirm the target issue and comment content before executing. |
| `LINEAR_CREATE_LINEAR_ISSUE` | Create linear issue | Creates 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. All UUID parameters (state_id, assignee_id, cycle_id, label_ids, project_id) must belong to the same team as team_id. The created issue's id is returned in data.id — capture it for use as parent_id in sub-issues or follow-up operations. No template_id field exists; expand templates manually into title and description before calling. |
| `LINEAR_CREATE_LINEAR_ISSUE_RELATION` | Create issue relation | Create a relationship between two Linear issues using the issueRelationCreate mutation. Use this to establish connections like 'blocks', 'duplicate', or 'related' between issues. |
| `LINEAR_CREATE_LINEAR_LABEL` | Create a label | Creates a new label in Linear for a specified team, used to categorize and organize issues. Label names must be unique within each team. If a label with the same name already exists, the existing label will be returned. Both new and existing labels return the same object structure; check the label's `createdAt` or compare IDs to determine if creation occurred. |
| `LINEAR_CREATE_LINEAR_PROJECT` | Create Project | Creates a new Linear project with specified name and team associations. |
| `LINEAR_CREATE_PROJECT_MILESTONE` | Create Project Milestone | Tool to create a project milestone in Linear with a name and optional target date and sort order. Use when you need to add milestones to track progress within a project. |
| `LINEAR_CREATE_PROJECT_UPDATE` | Create Project Update | Tool to create a project status update post for a Linear project. Use when you need to post progress updates, status reports, or announcements for a project. |
| `LINEAR_CREATE_TEAM` | Create Team | Creates a new team in Linear with the specified name and key. Use this action when you need to create a new organizational unit or work group in a Linear workspace. Teams are fundamental organizational structures in Linear that group issues, projects, and members together. Once created, the team's key becomes the prefix for all issues created within that team (e.g., 'ENG-123'). IMPORTANT: The key must be unique across the workspace and cannot be changed after creation. |
| `LINEAR_DELETE_LINEAR_ISSUE` | Delete issue | Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent. Archiving is permanent with no built-in undo — confirm the issue identifier and title with the user before executing, especially in bulk operations. |
| `LINEAR_GET_ATTACHMENT` | Download issue files | Downloads a Linear Attachment record or a private upload embedded in issue/comment Markdown; `file_name` must include the correct extension. |
| `LINEAR_GET_COMMENT` | Get a comment | Retrieves a single Linear comment by its unique ID. Returns comprehensive details including the comment body, author, timestamps, associated issue, and thread information. Use this action when you need to fetch details about a specific comment, such as when displaying comment information, checking comment status, or retrieving comment content for processing. The comment ID can be obtained from issue queries, comment lists, or comment creation responses. |
| `LINEAR_GET_CURRENT_USER` | Get current user | Gets 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. Use the returned `id` field (nested under `data.viewer`) for downstream Linear operations requiring user ID filtering. To search or compare other workspace members, use LINEAR_LIST_LINEAR_USERS instead. |
| `LINEAR_GET_CYCLES_BY_TEAM_ID` | Get cycles by team ID | Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints). Results are team-scoped to the given team_id. To identify the active cycle, check that the current date (in UTC) falls between a cycle's startAt and endAt fields; either field may be null. Results may be paginated — follow page_info cursors to retrieve all cycles. |
| `LINEAR_GET_ISSUE_DEFAULTS` | Get create issue default params | Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms. |
| `LINEAR_GET_LINEAR_ISSUE` | Get Linear issue | Retrieves 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.comments.nodes for comment IDs), subscribers, and due date. Embedded screenshots are uploads.linear.app URLs in description/comment Markdown, not Attachment records; download them with LINEAR_GET_ATTACHMENT's upload_url input. Does not include parent, milestone, cycle, or relation graphs—use LINEAR_RUN_QUERY_OR_MUTATION for those. Optional fields (labels, project, state, assignee, cycle) may be null; guard against null when accessing nested properties. Returns null or 'Entity not found' for invalid IDs, cross-workspace IDs, or restricted teams. Rate limit: ~60 req/min; HTTP 429 on excess—apply exponential backoff and respect Retry-After headers. |
| `LINEAR_GET_LINEAR_PROJECT` | Get Linear project | Retrieves a single Linear project by its unique identifier. Use when verifying a newly created or updated project, or when fetching detailed project information by ID. |
| `LINEAR_GET_PROJECT_UPDATE` | Get Project Update | Retrieves a specific project update by its unique identifier. Use when you need to fetch details about a specific project status update, including the update content, health status, timestamps, and associated project information. This action is useful when verifying a newly created project update or retrieving historical project update information. |
| `LINEAR_LIST_COMMENTS` | List comments | Lists comments from Linear workspace accessible to the authenticated user. Use this action when you need to retrieve comments for analysis, reporting, or tracking discussions across issues. The response includes comment content, timestamps, author information, and associated issue details. Supports pagination for large result sets. |
| `LINEAR_LIST_ISSUE_DRAFTS` | List issue drafts | Tool to list issue drafts. Use when you need to fetch draft issues for review or further editing. Check `pageInfo.hasNextPage` in the response to determine if additional drafts exist beyond the current page. |
| `LINEAR_LIST_ISSUES_BY_TEAM_ID` | List issues by team ID | Tool to list all issues for a specific Linear team, scoped by team ID. Use when you need to retrieve issues belonging to a particular team without fetching workspace-wide issues. This is more efficient than workspace-wide listing followed by client-side filtering. |
| `LINEAR_LIST_LINEAR_CYCLES` | Get all cycles | Retrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied. In large multi-team workspaces this produces heavy responses — filter client-side by team ID and date range using each cycle's startsAt/endsAt fields. Cycles are team-scoped; always group by team ID to avoid mixing sprints across teams. To identify the active sprint, verify the current UTC timestamp falls between startsAt and endsAt, and handle null startsAt/endsAt defensively. Timestamps are UTC. Results may be paginated; follow pageInfo.endCursor and hasNextPage until hasNextPage is false to avoid truncated lists. |
| `LINEAR_LIST_LINEAR_ISSUES` | List Linear issues | Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned. Can filter by assignee_id. Only project_id and assignee_id server-side filters are supported; label, state, team, cycle, or date filters must be done client-side or via LINEAR_RUN_QUERY_OR_MUTATION. Response is a flat issues array plus page_info object (not GraphQL nodes/pageInfo). Fields like cycle membership, dueDate, completedAt, comments, and attachments are absent; use LINEAR_GET_LINEAR_ISSUE for enrichment. state and labels are nested objects (labels as labels.nodes array). Response order is not guaranteed; sort client-side after collecting all pages. No team_id filter; scope by project_id or use LINEAR_RUN_QUERY_OR_MUTATION. |
| `LINEAR_LIST_LINEAR_LABELS` | Get labels | Retrieves labels from Linear. If team_id is provided, returns labels for that specific team; if omitted, returns all labels across the workspace. Label names are not unique across teams — always use returned IDs, not names, and track each label ID with its team ID. In large workspaces, results may paginate; follow pageInfo.hasNextPage and pageInfo.endCursor to retrieve all labels. |
| `LINEAR_LIST_LINEAR_PROJECTS` | List linear projects | Retrieves all projects from the Linear account. Returns a flat array (not a GraphQL connection) with fields id and name; use LINEAR_RUN_QUERY_OR_MUTATION for progress, state, issues, or team linkage. No server-side filtering: all workspace projects are returned regardless of team or name — filter client-side. Multiple projects can share identical names; always confirm project_id before downstream use. Results are permission-scoped to the connected user. Pagination: loop while page_info.hasNextPage is true, passing page_info.endCursor as after, or results will be silently truncated. HTTP 429 may occur in large workspaces; apply exponential backoff between calls. |
| `LINEAR_LIST_LINEAR_STATES` | 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. Returned state IDs are team-scoped — never reuse a stateId across different teams, as this causes validation errors or 'Entity not found' failures in tools like LINEAR_UPDATE_ISSUE. State names (e.g., 'Done', 'In Progress') are non-unique across teams; always resolve names to IDs via this tool for the specific team_id before using them in filters or mutations. Uses cursor-based pagination via pageInfo.hasNextPage and endCursor; iterate until hasNextPage is false to avoid missing states in large workspaces. Always fetch fresh state IDs rather than hardcoding or reusing stale values. |
| `LINEAR_LIST_LINEAR_TEAMS` | Get teams | Retrieves all teams with their members and projects. Use stable team IDs or keys (not display names) for subsequent operations — names are non-unique. Results reflect only teams visible to the authenticated token scope; missing teams or members indicate permission limits. Large workspaces paginate via pageInfo.hasNextPage/endCursor — incomplete pagination silently drops teams or members. Members may belong to multiple teams; deduplicate user IDs when aggregating. Use LINEAR_GET_ALL_LINEAR_TEAMS instead when only identifiers are needed. |
| `LINEAR_LIST_LINEAR_USERS` | List Linear users | Lists all workspace users (not team-scoped) with their IDs, names, emails, and active status. Display names are non-unique — use email to disambiguate before extracting an ID. Only assign users with `active: true`. Returned IDs are UUID strings; pass them as-is to fields like `assignee_id` — never substitute names, emails, or tokens. When joining with other tools, always join on IDs. |
| `LINEAR_LIST_PROJECT_UPDATES` | List project updates | Retrieves all project updates from the Linear workspace. Project updates are status posts written by team members to communicate project progress, blockers, and health. Use when you need to fetch project update history, track project health over time, or review team communication. Returns a paginated list with fields including id, body, health, createdAt, url, user, and project. Results are permission-scoped to the connected user — only updates from accessible projects are returned. Pagination: loop while page_info.hasNextPage is true, passing page_info.endCursor as after, or results will be silently truncated. HTTP 429 may occur in large workspaces; apply exponential backoff between calls. |
| `LINEAR_REMOVE_ISSUE_LABEL` | Remove label from Linear issue | Removes a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue. Operation is irreversible — obtain explicit user approval before executing. Use this tool instead of LINEAR_UPDATE_ISSUE to avoid replacing the entire label set. |
| `LINEAR_REMOVE_REACTION` | Remove reaction from comment | Tool to remove a reaction on a comment. Use when you have a reaction ID and need to delete it. |
| `LINEAR_RESOLVE_COMMENT` | Resolve comment | Marks a Linear comment as resolved. This action is used when a comment thread or discussion has been addressed and should be marked as complete. Use this action when you need to resolve a comment after addressing the feedback or discussion it represents. The comment remains visible but is marked as resolved with a timestamp and the resolving user's information. |
| `LINEAR_RUN_QUERY_OR_MUTATION` | Run Query or Mutation | Execute any GraphQL query or mutation against Linear's API. USE WHEN: No dedicated action exists, need complex filtering, custom fields, or schema discovery. *** INTROSPECTION FIRST - NEVER GUESS FIELD NAMES *** Run introspection before unknown operations: - query { __type(name: "Issue") { fields { name } } } - query { __type(name: "Mutation") { fields { name } } } Linear uses nested objects (project { id }), NOT scalar IDs (projectId). KEY: All IDs are UUIDs. Filter: { field: { eq: value } }. Pagination: nodes[] + pageInfo. |
| `LINEAR_SEARCH_ISSUES` | Search Linear issues | Search Linear issues using full-text search across identifier, title, and description. Use when you need to find issues by keywords or specific identifiers. Note: This endpoint only supports full-text search; for structured filtering by team, project, assignee, state, or labels, use LIST_ISSUES_BY_TEAM_ID instead. |
| `LINEAR_UNARCHIVE_PROJECT_UPDATE` | Unarchive Project Update | Unarchive a previously archived project update in Linear. Use this action when you need to restore an archived project update to make it visible and active again. Archived project updates are hidden from normal views but can be restored using this action. Use when a project update was archived by mistake or needs to be brought back into active use. |
| `LINEAR_UNRESOLVE_COMMENT` | Unresolve a comment | Unresolves a previously resolved Linear comment, marking it as requiring attention again. Use this action when you need to reopen a comment thread that was previously marked as resolved. This is useful when additional discussion is needed or the resolution was premature. |
| `LINEAR_UPDATE_ISSUE` | Update issue | Updates 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.) must be valid UUIDs — only `issueId` accepts key format (e.g., 'ENG-123'). All updated fields are fully overwritten, not merged; omit any field you do not intend to change. |
| `LINEAR_UPDATE_LINEAR_COMMENT` | Update a comment | Tool to update an existing Linear comment's body text. Use when you need to edit or modify the content of a previously created comment. |
| `LINEAR_UPDATE_LINEAR_PROJECT` | Update Project | Tool to update an existing Linear project. Use when you need to modify project properties like name, description, state, dates, or lead. All fields except project_id are optional - only provide the fields you want to update. |
| `LINEAR_UPDATE_PROJECT_UPDATE` | Update Project Update | Tool to update an existing Linear project update post. Use this action when you need to modify a project update's content, health status, or diff visibility settings. All fields except the update ID are optional - only provide the fields you want to update. Changes are immediately visible to all team members viewing the project. |
| `LINEAR_UPDATE_TEAM` | Update Team | Updates an existing Linear team's settings and configuration. Use when you need to modify team properties like name, description, key, cycle settings, workflow states, or other team-level configurations. All fields except team_id are optional - only provide the fields you want to update. |
| `LINEAR_VALIDATE_CREDENTIAL` | Validate credential | Validates the Linear API credentials by checking if the authentication token can successfully query the current user. Use this action when you need to verify that API credentials are valid before performing other operations, or to confirm that authentication is working correctly. This is particularly useful for connection testing, credential verification flows, or troubleshooting authentication issues. |
| `LINEAR_WHO_AM_I` | Who Am I | Return the identity (name, email) of the connected Linear account. |

## Supported Triggers

| Trigger slug | Name | Description |
|---|---|---|
| `LINEAR_COMMENT_EVENT_TRIGGER` | Comment Received Trigger | Triggered when a comment is received. |
| `LINEAR_ISSUE_CREATED_TRIGGER` | Issue Created Trigger | Triggered when a new issue is created. |
| `LINEAR_ISSUE_UPDATED_TRIGGER` | Issue Updated Trigger | Triggered when an issue is updated. For example labels are changed, issue status is changed, etc. |
| `LINEAR_PRIVATE_TEAM_COMMENT_CREATED` | Private Team Comment Created | Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token). |
| `LINEAR_PRIVATE_TEAM_ISSUE_CREATED` | Private Team Issue Created | Fires when a new issue appears in a private Linear team (polled with the connected user's token). |
| `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED` | Private Team Issue Properties Updated | Fires when properties on an issue change in a private Linear team (polled with the connected user's token). |
| `LINEAR_PROJECT_CREATED` | Project Created | Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear. |
| `LINEAR_PROJECT_PROPERTIES_UPDATED` | Project Properties Updated | Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token. |
| `LINEAR_PROJECT_UPDATE_POSTED` | Project Update Posted | Fires when a project status update is posted on the Linear project's Updates tab. Covers projects in both public and private teams — polls with the connected user's token. |
| `LINEAR_PUBLIC_TEAM_COMMENT_CREATED` | Public Team Comment Created | Fires when a new comment is posted on a *public-team* Linear issue. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_COMMENT_CREATED`. |
| `LINEAR_PUBLIC_TEAM_ISSUE_CREATED` | Public Team Issue Created | Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`. |
| `LINEAR_PUBLIC_TEAM_ISSUE_PROPERTIES_UPDATED` | Public Team Issue Properties Updated | Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`. |

## Creating MCP Server - Stand-alone vs Composio SDK

The Linear MCP server provides comprehensive access to Linear operations through Composio. Once connected, you can perform all major Linear actions directly from Codex using natural language commands.

## Complete Code

None listed.

## Conclusion

### Conclusion
You've successfully integrated Linear with Codex using Composio's MCP server. Now you can interact with Linear directly from your terminal, VS Code, or the Codex App using natural language commands.
Key benefits of this setup:
- Seamless integration across CLI, VS Code, and standalone app
- Natural language commands for Linear operations
- Managed authentication through Composio
- Access to 20,000+ tools across 1500+ apps for cross-app workflows
- CodeAct workbench for complex tool chaining
Next steps:
- Try asking Codex to perform various Linear operations
- Explore cross-app workflows by connecting more toolkits
- Build automation scripts that leverage Codex's AI capabilities

## How to build Linear MCP Agent with another framework

- [Claude Code](https://composio.dev/toolkits/linear/framework/claude-code)
- [Cursor](https://composio.dev/toolkits/linear/framework/cursor)
- [ChatGPT](https://composio.dev/toolkits/linear/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/linear/framework/claude-cowork)
- [Antigravity](https://composio.dev/toolkits/linear/framework/antigravity)
- [OpenAI Agents SDK](https://composio.dev/toolkits/linear/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/linear/framework/claude-agents-sdk)
- [Grok Bot](https://composio.dev/toolkits/linear/framework/grok-bot)
- [Muse](https://composio.dev/toolkits/linear/framework/muse)
- [Kimi Code](https://composio.dev/toolkits/linear/framework/kimi)
- [Grok Build](https://composio.dev/toolkits/linear/framework/grok-build)
- [VS Code](https://composio.dev/toolkits/linear/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/linear/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/linear/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/linear/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/linear/framework/atomic-agent)
- [CLI](https://composio.dev/toolkits/linear/framework/cli)
- [Google ADK](https://composio.dev/toolkits/linear/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/linear/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/linear/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/linear/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/linear/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/linear/framework/crew-ai)
- [Pydantic AI](https://composio.dev/toolkits/linear/framework/pydantic-ai)
- [AutoGen](https://composio.dev/toolkits/linear/framework/autogen)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - 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](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - 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](https://composio.dev/toolkits/asana) - 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.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Jira](https://composio.dev/toolkits/jira) - Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [AirOps MCP](https://composio.dev/toolkits/airops_mcp) - AirOps MCP is AirOps' managed content platform exposing brand context, knowledge bases, and workflows. Use it to give agents brand-aware content, automate content workflows, and track Brand Kit edits.
- [Amazing Marvin](https://composio.dev/toolkits/amazing_marvin) - Amazing Marvin is a personal productivity app for tasks, projects, habits, planning, time tracking, and rewards. It helps you build a flexible workflow that matches how you actually work.
- [AnyDB](https://composio.dev/toolkits/any_db) - AnyDB is a flexible collaborative database platform for organizing records, files, and automated workflows. It helps teams centralize data, collaborate on records, and automate routine tasks.
- [ApptiveGrid](https://composio.dev/toolkits/apptivegrid) - ApptiveGrid is a collaborative no-code database and app platform for spaces, grids, forms, and structured records. It helps teams organize operational data, collect inputs, and build lightweight business apps without custom backend work.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Atlassian MCP](https://composio.dev/toolkits/atlassian_mcp) - Atlassian Rovo MCP connects agents to Jira, Jira Service Management, Confluence, Bitbucket, Compass, and Teamwork Graph workflows. It lets teams surface and act on Atlassian data while respecting existing user permissions.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.

## Frequently Asked Questions

### 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 Codex?

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

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)