# Linear MCP

```json
{
  "name": "Linear MCP",
  "slug": "linear_mcp",
  "url": "https://composio.dev/toolkits/linear_mcp",
  "markdown_url": "https://composio.dev/toolkits/linear_mcp.md",
  "logo_url": "https://logos.composio.dev/api/linear_mcp",
  "categories": [
    "productivity & project management"
  ],
  "is_composio_managed": false,
  "updated_at": "2026-09-24T15:42:59.586Z"
}
```

![Linear MCP logo](https://logos.composio.dev/api/linear_mcp)

## Description

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Linear MCP or direct API to find issues, create and update issues, manage projects, and post comments through natural language.

## Summary

Linear MCP is Linear's interface for managing issues, projects, comments, and planning objects within a workspace.
It centralizes planning data and simplifies tracking, prioritization, and collaboration across teams.

## Categories

- productivity & project management

## Toolkit Details

- Tools: 67

## Images

- Logo: https://logos.composio.dev/api/linear_mcp

## Authentication

- **Dcr Oauth**
  - Type: `custom`
  - Description: Dcr Oauth authentication for Linear MCP.
  - Setup:
    - Configure Dcr Oauth credentials for Linear MCP.
    - Use the credentials when creating an auth config in Composio.

## Suggested Prompts

- List all open issues assigned to me
- Create a new issue from template
- Add comment to issue by ID

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `LINEAR_MCP_CREATE_ATTACHMENT` | Create attachment | Deprecated fallback for tiny files only. Accepts base64 file content, verifies SHA-256 checksum, and uploads it through the MCP worker. Prefer `prepare_attachment_upload` plus direct PUT plus `create_attachment_from_upload`. CRITICAL: Do not print base64Content and then copy it into this tool call. Opaque base64 copied through model-visible text is easy to corrupt. Generate base64Content mechanically from the source bytes and pass it through a programmatic argument construction path whenever available. Before calling this tool, verify the values are consistent: Unix-like shells: file="/path/to/file" base64Content=$(base64 < "$file" \| tr -d '\\n\\r') sha256=$(shasum -a 256 "$file" \| awk '{print $1}') decodedSha256=$(printf '%s' "$base64Content" \| base64 -d \| shasum -a 256 \| awk '{print $1}') size=$(wc -c < "$file" \| tr -d ' ') # optional; stat can also get file byte size decodedSize=$(printf '%s' "$base64Content" \| base64 -d \| wc -c \| tr -d ' ') PowerShell: $file = 'C:\\path\\to\\file' $bytes = [IO.File]::ReadAllBytes($file) $base64Content = [Convert]::ToBase64String($bytes) $sha256 = (Get-FileHash -Algorithm SHA256 -Path $file).Hash.ToLower() $size = $bytes.Length # optional $decoded = [Convert]::FromBase64String($base64Content) $decodedStream = [IO.MemoryStream]::new($decoded) $decodedSha256 = (Get-FileHash -Algorithm SHA256 -InputStream $decodedStream).Hash.ToLower() $decodedSize = $decoded.Length decodedSha256 must equal sha256. If you pass size, decodedSize must equal size. Pass `sha256`. Passing `size` is optional, but recommended for clearer mismatch errors. |
| `LINEAR_MCP_CREATE_ATTACHMENT_FROM_UPLOAD` | Create attachment from upload | Link an already-uploaded Linear assetUrl to an existing issue as an attachment. Use this only after: 1. prepare_attachment_upload returned an assetUrl and uploadRequest. 2. The client successfully PUT raw file bytes to uploadRequest.url. This tool does not upload file content. It only creates the Linear attachment row. If the direct upload failed or the signed URL expired, rerun prepare_attachment_upload and upload again. |
| `LINEAR_MCP_CREATE_INITIATIVE_LABEL` | Create initiative label | Create a new Linear initiative label |
| `LINEAR_MCP_CREATE_ISSUE_LABEL` | Create issue label | Create a new Linear issue label |
| `LINEAR_MCP_DELETE_ATTACHMENT` | Delete attachment | Delete an attachment by ID |
| `LINEAR_MCP_DELETE_COMMENT` | Delete comment | Delete a Linear comment. Inline description comments (those with non-null `quotedText`) anchor a mark in the editor, so their root cannot be deleted — delete the replies individually or resolve the thread instead. |
| `LINEAR_MCP_DELETE_CUSTOMER` | Delete customer | Delete a customer in Linear |
| `LINEAR_MCP_DELETE_CUSTOMER_NEED` | Delete customer need | Archive a customer need in Linear |
| `LINEAR_MCP_DELETE_DIFF_COMMENT` | Delete diff comment | Delete a comment or persisted draft from a Linear diff |
| `LINEAR_MCP_DELETE_STATUS_UPDATE` | Delete status update | Delete (archive) a project or initiative status update. |
| `LINEAR_MCP_EXTRACT_IMAGES` | Extract images | Extract and fetch images from markdown content. Use this to view screenshots, diagrams, or other images embedded in Linear issues, comments, or documents. Pass the markdown content (e.g., issue description) and receive the images as viewable data. |
| `LINEAR_MCP_GET_AGENT_SKILL` | Get agent skill | Retrieve a Linear Agent skill by ID, including its full markdown instructions. |
| `LINEAR_MCP_GET_ATTACHMENT` | Get attachment | Retrieve an attachment's content by ID. |
| `LINEAR_MCP_GET_DIFF` | Get diff | Exact lookup for a Linear diff. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs. |
| `LINEAR_MCP_GET_DIFF_THREADS` | Get diff threads | Exact lookup for diff threads and the authenticated user's drafts. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs. |
| `LINEAR_MCP_GET_DOCUMENT` | Get document | Retrieve a Linear document by ID or slug |
| `LINEAR_MCP_GET_INITIATIVE` | Get initiative | Retrieve detailed information about a specific initiative in Linear |
| `LINEAR_MCP_GET_ISSUE` | Get issue | Retrieve detailed information about an issue by ID, including attachments, git branch name, and active Triage Intelligence suggestions when the issue is in triage |
| `LINEAR_MCP_GET_ISSUE_STATUS` | Get issue status | Retrieve detailed information about an issue status in Linear by name or ID |
| `LINEAR_MCP_GET_MILESTONE` | Get milestone | Retrieve details of a specific milestone by ID or name |
| `LINEAR_MCP_GET_PROJECT` | Get project | Retrieve details of a specific project in Linear |
| `LINEAR_MCP_GET_RELEASE` | Get release | Retrieve details of a release by ID or slug. |
| `LINEAR_MCP_GET_RELEASE_NOTE` | Get release note | Retrieve release notes by ID or slug, including markdown content. |
| `LINEAR_MCP_GET_STATUS_UPDATES` | Get status updates | List or get project/initiative status updates. Pass `id` to get a specific update, or filter to list. |
| `LINEAR_MCP_GET_TEAM` | Get team | Retrieve details of a specific Linear team |
| `LINEAR_MCP_GET_TEMPLATE` | Get template | Retrieve a Linear template by ID or name: the content it pre-fills, the ids it applies, its sub-issues, and its form fields. Pass the template to save_issue or save_project to apply it. References come back as ids, so read a name with the matching tool when you need one. A form template collects its answers through a form, so applying one here creates an issue with the form unanswered. |
| `LINEAR_MCP_GET_USER` | Get user | Retrieve details of a specific Linear user |
| `LINEAR_MCP_GET_WORKSPACE` | Get workspace | Retrieve the connected Linear workspace |
| `LINEAR_MCP_LIST_AGENT_SKILLS` | List agent skills | List Linear Agent skills available to the authenticated user. |
| `LINEAR_MCP_LIST_COMMENTS` | List comments | List comments on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. Provide exactly one of `issueId`, `projectId`, `initiativeId`, `documentId`, `milestoneId`, or `statusUpdateId`. For issues, projects, and initiatives this returns both top-level discussion threads and inline description comments. Inline (anchored) comments carry a non-null `quotedText` set to the snippet of description text they reference. Returned comments include `author` and nullable `onBehalfOf`; when set, `onBehalfOf` identifies the user the agent author acted for. |
| `LINEAR_MCP_LIST_CUSTOMERS` | List customers | List customers in the user's Linear workspace |
| `LINEAR_MCP_LIST_CYCLES` | List cycles | Retrieve cycles for a specific Linear team |
| `LINEAR_MCP_LIST_DIFFS` | List diffs | List Linear diff pull requests visible to the authenticated user |
| `LINEAR_MCP_LIST_DOCUMENTS` | List documents | List documents in the user's Linear workspace |
| `LINEAR_MCP_LIST_INITIATIVE_LABELS` | List initiative labels | List available initiative labels in the Linear workspace |
| `LINEAR_MCP_LIST_INITIATIVES` | List initiatives | List initiatives in the user's Linear workspace |
| `LINEAR_MCP_LIST_ISSUE_LABELS` | List issue labels | List available issue labels in a Linear workspace or team |
| `LINEAR_MCP_LIST_ISSUES` | List issues | List issues in the user's Linear workspace, including active Triage Intelligence suggestions for issues in triage. For my issues, use "me" as the assignee. Use "null" for no assignee. |
| `LINEAR_MCP_LIST_ISSUE_STATUSES` | List issue statuses | List available issue statuses in a Linear team |
| `LINEAR_MCP_LIST_MILESTONES` | List milestones | List all milestones in a Linear project |
| `LINEAR_MCP_LIST_PROJECT_LABELS` | List project labels | List available project labels in the Linear workspace |
| `LINEAR_MCP_LIST_PROJECTS` | List projects | List projects in the user's Linear workspace |
| `LINEAR_MCP_LIST_RELEASE_NOTES` | List release notes | List release notes in the workspace, optionally filtered by pipeline or covered release. |
| `LINEAR_MCP_LIST_RELEASE_PIPELINES` | List release pipelines | List release pipelines in the workspace. |
| `LINEAR_MCP_LIST_RELEASES` | List releases | List releases in the workspace, with optional filtering by pipeline, stage, version, and text. |
| `LINEAR_MCP_LIST_TEAMS` | List teams | List teams in the user's Linear workspace |
| `LINEAR_MCP_LIST_TEMPLATES` | List templates | List the Linear issue, project, and document templates available to the authenticated user. Use this to find the template a team expects, then call get_template for its content. |
| `LINEAR_MCP_LIST_USERS` | List users | Retrieve users in the Linear workspace |
| `LINEAR_MCP_MERGE_DIFF` | Merge diff | Merge a Linear diff or add it to the repository's merge queue |
| `LINEAR_MCP_PREPARE_ATTACHMENT_UPLOAD` | Prepare attachment upload | Prepare a direct Linear file upload for an existing issue. Workflow: 1. Call this tool with issue, filename, contentType, and size. 2. Upload raw bytes with PUT to uploadRequest.url outside MCP. 3. All headers in uploadRequest.headers are part of the signed request, so send them verbatim. 4. After PUT succeeds, call create_attachment_from_upload with assetUrl to link it to the issue. Do not base64-encode or transform the file. Use curl --data-binary @path or fetch(url, { method: 'PUT', body: blob }). Omitting or modifying any signed header, including casing, will return HTTP 403. The signed URL must be used within 60 seconds or it will expire. Upload sequencing: Prepare, PUT, and finalize one file before calling this tool for another file. Do not batch multiple prepare_attachment_upload calls before starting the PUTs because earlier signed URLs can expire while later files are prepared. Example: curl -X PUT --data-binary @file.png \\ -H "content-type: image/png" \\ -H "x-goog-content-length-range: N,N" \\ -H "cache-control: public, max-age=31536000" \\ -H 'Content-Disposition: attachment; filename="file.png"' \\ "" |
| `LINEAR_MCP_RESOLVE_DIFF_THREAD` | Resolve diff thread | Resolve or reopen a top-level comment thread on a Linear diff |
| `LINEAR_MCP_SAVE_COMMENT` | Save comment | Create or update a comment on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. If `id` is provided, updates the existing comment; otherwise creates a new one. To start a new thread, pass `body` and exactly one of `issueId`, `projectId`, `initiativeId`, `documentId`, `milestoneId`, or `statusUpdateId` — comments on issues/projects/initiatives become top-level discussion threads; comments on documents/milestones become description comments. A status update holds a single thread, so a comment on an update that already has one is added to it as a reply. To reply to an existing thread, pass `parentId` and `body`; the reply inherits the parent's thread type, so no entity reference is needed. Parent reference fields are ignored when `id` or `parentId` is provided (`statusUpdateType` is rejected instead). |
| `LINEAR_MCP_SAVE_CUSTOMER` | Save customer | Create or update a Linear customer. If `id` is provided, updates the existing customer; otherwise creates a new one. When creating, `name` is required. |
| `LINEAR_MCP_SAVE_CUSTOMER_NEED` | Save customer need | Create or update a customer need (request) in Linear. If `id` is provided, updates the existing need; otherwise creates a new one. When creating, `body` is required. |
| `LINEAR_MCP_SAVE_DIFF_COMMENT` | Save diff comment | Create, reply to, or edit a comment or persisted draft on a Linear diff. Set draft to true to save without submitting. Provide draftId to edit or submit a persisted draft, and commentId only to edit a submitted comment. Submitting an inline draft reuses its saved anchor; submitting a reply draft requires parentId again. |
| `LINEAR_MCP_SAVE_DOCUMENT` | Save document | Create or update a Linear document. If `id` is provided, edits the existing document; otherwise creates a new one. When creating, `title` is required and exactly one parent (`project`, `issue`, `initiative`, `cycle`, or `team`) must be specified. On update, passing a parent reparents the document. To change parts of the content without resending all of it, pass `patch` instead of `content`. |
| `LINEAR_MCP_SAVE_INITIATIVE` | Save initiative | Create or update a Linear initiative. If `id` is provided, updates the existing initiative; otherwise creates a new one. When creating, `name` is required. To change parts of the description without resending all of it, pass `patch` instead of `description`. |
| `LINEAR_MCP_SAVE_ISSUE` | Save issue | Create or update a Linear issue. If `id` is provided, updates the existing issue; otherwise creates a new one. When creating, `team` is required, and `title` is required unless `template` is set. Note: use `assignee` (not `assigneeId`) to set the assignee — it accepts a user ID, name, email, or "me". |
| `LINEAR_MCP_SAVE_MILESTONE` | Save milestone | Create or update a milestone in a Linear project. If `id` is provided, updates the existing milestone; otherwise creates a new one. When creating, `name` is required. |
| `LINEAR_MCP_SAVE_PROJECT` | Save project | Create or update a Linear project. If `id` is provided, updates the existing project; otherwise creates a new one. When creating, `name` and at least one team (via `addTeams` or `setTeams`) are required. Pass `template` to create the project from a project template. To change parts of the description without resending all of it, pass `patch` instead of `description`. |
| `LINEAR_MCP_SAVE_RELEASE` | Save release | Create or update a release. If `id` is provided, updates the existing release; otherwise creates a new one. When creating, `name` and `pipeline` are required. Release status is modeled as the release pipeline stage. |
| `LINEAR_MCP_SAVE_RELEASE_NOTE` | Save release note | Create or update release notes. If `id` is provided, updates the existing release notes; otherwise creates a new one. When creating, `pipeline` and either `releases` or a release range are required. To change parts of the content without resending all of it, pass `patch` instead of `content`. |
| `LINEAR_MCP_SAVE_STATUS_UPDATE` | Save status update | Create or update a project/initiative status update. Omit `id` to create, provide `id` to update. |
| `LINEAR_MCP_SEARCH_DOCUMENTATION` | Search documentation | Search Linear's documentation to learn about features and usage |
| `LINEAR_MCP_SHARE_ISSUE` | Share issue | Share an issue with a workspace user who cannot otherwise access it. Use this tool only when the user explicitly asks to share the issue. |
| `LINEAR_MCP_SUBMIT_DIFF_REVIEW` | Submit diff review | Approve a Linear diff, request changes, or submit a review comment |
| `LINEAR_MCP_UNSHARE_ISSUE` | Unshare issue | Remove a workspace user's shared access to an issue. Use this tool only when the user explicitly asks to stop sharing the issue. |

## Supported Triggers

None listed.

## Installation and MCP Setup

### Path 1: SDK Installation

#### Path 1, Step 1: Install Composio

Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
```python
pip install composio composio_openai openai
```

```typescript
npm install @composio/core @composio/openai openai
```

#### Path 1, Step 2: Create a Composio session

Initialize Composio with the OpenAI Responses provider and create a session scoped to Linear MCP
```python
import json
from openai import OpenAI
from composio import Composio
from composio_openai import OpenAIResponsesProvider

composio = Composio(provider=OpenAIResponsesProvider())
client = OpenAI()

session = composio.create(user_id="your-user-id", toolkits=["linear_mcp"])
tools = session.tools()
```

```typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["linear_mcp"] });
const tools = await session.tools();
```

#### Path 1, Step 3: Run Linear MCP tools with your agent

Send a request, execute the Linear MCP tool calls through the session, and print the final answer
```python
response = client.responses.create(
    model="gpt-5.6-sol",
    tools=tools,
    input=[{"role": "user", "content": "List all open issues assigned to me"}],
)

while True:
    tool_calls = [o for o in response.output if o.type == "function_call"]
    if not tool_calls:
        break
    results = composio.provider.handle_tool_calls(response=response, session=session)
    response = client.responses.create(
        model="gpt-5.6-sol",
        tools=tools,
        previous_response_id=response.id,
        input=[
            {"type": "function_call_output", "call_id": call.call_id, "output": json.dumps(results[i])}
            for i, call in enumerate(tool_calls)
        ],
    )

print(response.output_text)
```

```typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "List all open issues assigned to me" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
```

### Path 2: MCP Server Setup

#### Path 2, Step 1: Install Composio

Install the Composio SDK and your agent framework
```python
pip install composio claude-agent-sdk
```

```typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
```

#### Path 2, Step 2: Create a session with MCP enabled

Create a session scoped to Linear MCP and read its MCP URL and headers
```python
from composio import Composio

composio = Composio()
session = composio.create(user_id="your-user-id", toolkits=["linear_mcp"], mcp=True)
```

```typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["linear_mcp"],
  mcp: true,
});
```

#### Path 2, Step 3: Connect your agent to the MCP server

Pass the session's MCP URL and headers to your agent and run a Linear MCP request
```python
import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions, AssistantMessage, TextBlock

options = ClaudeAgentOptions(
    mcp_servers={
        "composio": {
            "type": "http",
            "url": session.mcp.url,
            "headers": session.mcp.headers,
        }
    },
    system_prompt="You are a helpful assistant with access to Linear MCP tools.",
    tools=[],
    allowed_tools=["mcp__composio__*"],
)

async def main():
    async with ClaudeSDKClient(options=options) as client:
        await client.query("List all open issues assigned to me")
        async for message in client.receive_response():
            if isinstance(message, AssistantMessage):
                for block in message.content:
                    if isinstance(block, TextBlock):
                        print(block.text)

asyncio.run(main())
```

```typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "List all open issues assigned to me",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
```

## Why Use Composio?

### 1. AI Native Linear MCP Integration

- Supports both Linear MCP and direct API based integrations
- Structured, LLM-friendly schemas for reliable tool execution
- Rich coverage for reading, writing, and querying your Linear MCP data

### 2. Managed Auth

- Built-in OAuth handling with automatic token refresh and rotation
- Central place to manage, scope, and revoke Linear MCP access
- Per user and per environment credentials instead of hard-coded keys

### 3. Agent Optimized Design

- Tools are tuned using real error and success rates to improve reliability over time
- Comprehensive execution logs so you always know what ran, when, and on whose behalf

### 4. Enterprise Grade Security

- Fine-grained RBAC so you control which agents and users can access Linear MCP
- Scoped, least privilege access to Linear MCP resources
- Full audit trail of agent actions to support review and compliance

## Use Linear MCP with any AI Agent Framework

Choose a framework you want to connect Linear MCP with:

- [ChatGPT](https://composio.dev/toolkits/linear_mcp/framework/chatgpt)
- [Claude Cowork](https://composio.dev/toolkits/linear_mcp/framework/claude-cowork)
- [Hermes](https://composio.dev/toolkits/linear_mcp/framework/hermes-agent)
- [Atomic Agent](https://composio.dev/toolkits/linear_mcp/framework/atomic-agent)

## 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.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [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.

## Frequently Asked Questions

### Do I need my own developer credentials to use Linear MCP with Composio?

Yes, Linear MCP requires you to configure your own Dcr Oauth credentials. Once set up, Composio handles secure credential storage and management for you.

### Can I use multiple toolkits together?

Yes! Composio's Tool Router enables agents to use multiple toolkits. [Learn more](https://docs.composio.dev/tool-router/overview).

### Is Composio secure?

Composio is SOC 2 and ISO 27001 compliant with all data encrypted in transit and at rest. [Learn more](https://trust.composio.dev).

### What if the API changes?

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

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