# How to connect Linear to Grok Bot

```json
{
  "title": "How to connect Linear to Grok Bot",
  "toolkit": "Linear MCP",
  "toolkit_slug": "linear_mcp",
  "framework": "Grok Bot",
  "framework_slug": "grok-bot",
  "url": "https://composio.dev/toolkits/linear_mcp/framework/grok-bot",
  "markdown_url": "https://composio.dev/toolkits/linear_mcp/framework/grok-bot.md",
  "updated_at": "2026-11-11T06:01:11.920Z"
}
```

## Introduction

Grok is xAI's assistant, and its bot builder lets you create a personal agent that holds context, runs skills, and connects to the apps you already use through plugins.
This guide explains how to connect Linear to a Grok bot using Composio Connect, which handles OAuth, token refresh, and reliability so you do not have to. You add Composio as a plugin, authenticate once, then ask your bot to work with Linear in plain language.

## Also integrate 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)

## TL;DR

Composio exposes 1,700+ apps to your Grok bot through a single connection, so you get:
- Connect to 1,700+ apps with on-demand tool loading, so you do not fill your context window with unnecessary tool definitions.
- Use programmatic tool calling through a remote workbench, letting the model write its own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
- Handle large tool responses outside the model context to keep conversations lean.

## Connect Linear MCP to Grok Bot

### Connecting Linear to Grok Bot
Once Grok Bot is set up, you connect Linear entirely from its interface, and the whole flow takes under a minute.
### Set up Grok Bot
Get access. Grok Bot is included with Cursor Ultra, Cursor Premium Teams, and SuperGrok Heavy. Get the desktop app for macOS or Windows from [x.ai/bot](https://x.ai/bot) and sign in. An iPhone companion app is also available, and your bots sync across devices.
Create a bot. Pick a suggested role or define your own, then give it a short name, one primary job, and a short description of how it should work. Focused bots work best, because a clear role gives the bot more useful context over time.
### Connect Linear
### 1. Add the Composio plugin
Click the button. The Composio listing on x.ai opens and launches Grok Bot for you. If the app does not open on its own, click Add to Grok Bot.
[Add to Grok Bot](https://x.ai/bot/plugin/32661537)
Grok Bot opens the Composio plugin, showing its connector and skills. Click Add.
### 2. Authenticate
Go to the Installed section and click the Composio entry. You'll see its connector and skills listed.
Click Authenticate. You'll be taken to the Composio consent screen. Review the access it requests and click Authorize. Composio handles the OAuth handshake for you, so you never touch API keys or tokens.
### 3. Connect your Linear account
Back in the chat, ask your bot to connect to Linear or give it any Linear task.
For example, ask it to:
- "List all open issues assigned to me"
- "Create a new issue from template"
- "Add comment to issue by ID"
It will prompt you to authenticate and authorize access.
That's it. Composio's tools are now available in your Grok bot, and your Linear account is ready to use.

## What is Grok Bot?

Grok is xAI's assistant, available as a chat interface and a bot builder for creating personal agents that run skills and connect to external apps.
With Composio Connect, your Grok bot can securely access apps like Linear through MCP without you sharing account credentials directly with the agent.

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

The Linear MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Linear account. It provides structured and secure access to your workspace issues, projects, initiatives, documents, cycles, releases, and discussions, so your agent can review work, inspect plans, track updates, manage comments, and organize attachments on your behalf.
- Issue and team tracking: Have your agent list issues, retrieve issue details, review available statuses and labels, and inspect the teams and users responsible for the work.
- Project and initiative visibility: Let the agent retrieve projects, initiatives, milestones, cycles, status updates, and related planning documents to help you understand current priorities.
- Comments and attachment management: Direct your agent to review comments, remove outdated comments, retrieve attachments, link uploaded files to issues, or delete attachments.
- Release and development review: Instruct your agent to retrieve releases and release notes, list visible pull request diffs, and inspect diff details or discussion threads.
- Workspace inbox and resources: Have your agent check Linear notifications, list available templates and agent skills, or retrieve details about the connected workspace.

## 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. Deprecated: use `save_initiative_label`, which can also update labels. |
| `LINEAR_MCP_CREATE_ISSUE_LABEL` | Create issue label | Create a new Linear issue label. Deprecated: use `save_issue_label`, which can also update labels. |
| `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_NOTIFICATIONS` | Get notifications | Get a page of notifications from the authenticated user's Linear inbox. |
| `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. A retired label carries `retiredAt` and cannot be applied to new initiatives. |
| `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. A retired label carries `retiredAt` and cannot be applied to new issues. |
| `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. A team-scoped label carries a `team` field; different teams can hold same-named labels, so check it before acting on an ID. A retired label carries `retiredAt` and cannot be applied to new projects. |
| `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_MARK_NOTIFICATION` | Mark notification | Mark a Linear inbox notification as read or unread, or snooze or unsnooze it. |
| `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_RESTORE_INITIATIVE_LABEL` | Restore initiative label | Restore a retired Linear initiative label, making it available for use on initiatives again. Restoring a label group also restores every child label, including any that were retired separately. |
| `LINEAR_MCP_RESTORE_ISSUE_LABEL` | Restore issue label | Restore a retired Linear issue label, making it available for use on issues again. Restoring a label group also restores every child label, including any that were retired separately. |
| `LINEAR_MCP_RESTORE_PROJECT_LABEL` | Restore project label | Restore a retired Linear project label, making it available for use on projects again. Restoring a label group also restores every child label, including any that were retired separately. |
| `LINEAR_MCP_RETIRE_INITIATIVE_LABEL` | Retire initiative label | Retire a Linear initiative label so it cannot be applied to new initiatives. The label stays visible on initiatives that already have it. Retiring a label group also retires its child labels. Undo with `restore_initiative_label`. |
| `LINEAR_MCP_RETIRE_ISSUE_LABEL` | Retire issue label | Retire a Linear issue label so it cannot be applied to new issues. The label stays visible on issues that already have it. Retiring a label group also retires its child labels. Undo with `restore_issue_label`. |
| `LINEAR_MCP_RETIRE_PROJECT_LABEL` | Retire project label | Retire a Linear project label so it cannot be applied to new projects. The label stays visible on projects that already have it. Retiring a label group also retires its child labels. Undo with `restore_project_label`. |
| `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_INITIATIVE_LABEL` | Save initiative label | Create or update a Linear initiative label. If `id` is provided, updates the existing label; otherwise creates a new one. When creating, `name` is required. |
| `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_ISSUE_LABEL` | Save issue label | Create or update a Linear issue label. If `id` is provided, updates the existing label; otherwise creates a new one. When creating, `name` is required. |
| `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_PROJECT_LABEL` | Save project label | Create or update a Linear project label. If `id` is provided, updates the existing label; otherwise creates a new one. When creating, `name` is required. |
| `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.

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

Once connected, your Grok bot can access the Linear MCP server through Composio to run the actions you authorize, using plain language in the chat.

## Complete Code

None listed.

## Conclusion

### Way Forward
Now that Linear is connected, extend your setup by connecting the other apps you already use every day, so your Grok bot 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.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single connection, your bot can coordinate multiple tools safely and reliably in one conversation.

## How to build Linear MCP Agent with another framework

- [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.
- [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.
- [Aha!](https://composio.dev/toolkits/aha) - Aha! is a product management platform for setting strategy, prioritizing ideas, and planning roadmaps. It helps product teams align goals with development work and make better decisions.
- [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.
- [Ambiguous MCP](https://composio.dev/toolkits/ambiguous_mcp) - Ambiguous MCP is a provider-hosted workspace service for documents, spreadsheets, tasks, CRM, calendar, mail, chat, and administration. It provides one workspace-scoped connection for managing these resources through natural language.
- [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.

## 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 Grok Bot?

Yes, you can. Grok Bot 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)