---
title: "Linear MCP in Slack: ask an AI teammate to find and update issues | Chickpea"
description: "Use Linear's MCP server from Slack. Give a channel an AI teammate connected to Linear, then ask it to file issues, read the cycle, and triage. Open source."
canonical: https://chickpea.co/connectors/linear
keyword: "Linear MCP in Slack"
verified: 2026-09-17
---

# A Linear teammate in Slack, running on Linear's MCP server.

> Chickpea gives a channel a named AI teammate that holds its own Linear connection. It signs in with OAuth and calls Linear's MCP server, so there is no client to configure and no token to paste. Ask it in Slack to file an issue, say what is left in the cycle, or clear the triage queue, and it answers in the thread.

Facts checked against the sources on September 17, 2026. The HTML page is at https://chickpea.co/connectors/linear; every connector is listed at https://chickpea.co/connectors; the site index for agents is at https://chickpea.co/llms.txt.

**Linear** (Linear Orbit, Inc., https://linear.app): Find, create, and update issues, projects, and workspace plans. Category: Project management. Lane: Vendor MCP server. Sign in: OAuth.

**Chickpea**: an open source Slack app that gives a workspace named AI teammates, each with its own handle, instructions, memory, connected accounts, schedules, and model, deployed to your own Cloudflare account or a Node host.

## What people ask it
The teammate in these examples is @pm, published to #eng.

### File an issue
- @pm file this thread in Linear as a bug on the Payments team, urgent
- @pm create an issue: the refund webhook retries forever. Assign it to Marco

A new issue is a small, reversible write, so it goes straight through. The reply names the identifier, the team, and the priority it set, with a link into Linear. Anything you leave out it asks about rather than guessing.

### Read the cycle
- @pm what is left in the current cycle, and is anything blocked
- @pm show me every urgent issue in Payments that nobody owns

Reads never need confirmation, and a long answer comes back as a table in the thread. What it can see is what the connected Linear account can see; signing in does not widen anyone.

### Triage and reassign
- @pm move ENG-477 to Marco and put it in this cycle
- @pm everything in triage that mentions refunds goes to Marco, in cycle 24

One issue changes on the spot. A change across several comes back as a list of what would move and waits for a yes. A write also needs the message you sent to name it, because a thread on its own cannot authorize one.

### Comment and close
- @pm comment on ENG-482 that the fix shipped behind a flag
- @pm close ENG-469, the copy landed this morning

A comment or one state change applies immediately. The teammate can only call tools the server answered with when the connection was made, so its reach is whatever Linear exposes to that account, never more.

### On a schedule
- @pm every Friday at 4pm Eastern, list what slipped out of the cycle
- @pm every weekday at 9am Pacific, post the urgent issues with no owner

A schedule saves on the spot. It needs an explicit time zone, runs under the Linear connection of the person who asked, and fails with a named reason rather than running if that connection is disconnected.

### Example conversations

**Create an issue**
> **Sofia:** @pm file this in Linear: checkout retries twice on a 402 and charges the card again. Payments team, bug, urgent.
> **@pm:** Filed ENG-482, Checkout retries a 402 and double-charges the card. Payments team, label bug, priority urgent, unassigned. I quoted this thread in the description. Open it in Linear

**What is in this cycle**
> **Marco:** @pm what’s left in the current cycle, and is anything blocked?
> **@pm:** Cycle 24 ends Friday. Five issues are still open and two are blocked, both waiting on the same infra ticket.
>
> | Issue | Title | Assignee | State |
> |---|---|---|---|
> | ENG-482 | Checkout double-charge | Priya | In progress |
> | ENG-474 | Retry queue backoff | Marco | Blocked |
> | ENG-477 | Refund webhook replay | Marco | Blocked |
> | ENG-469 | Card error copy | Dana | In review |
> | ENG-486 | Payment logs dashboard | Sofia | Todo |

**Triage the inbox**
> **Dana:** @pm move everything in Payments triage that mentions refunds onto Marco and put it in this cycle.
> **@pm:** Four issues match: ENG-477, ENG-489, ENG-491, ENG-494. Each would move to Marco and into cycle 24. That is a bulk change, so I will wait. Go ahead?
> Buttons: Yes, update all four · Show me them first

**Every Friday**
> **Priya:** @pm every Friday at 4pm Eastern, post what slipped out of the cycle here, with who owns each one.
> **@pm:** Saved. Every Friday at 4:00 PM Eastern I’ll list the Payments issues that did not close, with their owners, in #eng. First run is Fri Sep 18. It runs on your Linear connection, so say "pause the Friday digest" if you want it to stop.

## Connect Linear
1. In Chickpea Admin, open the teammate, then **Connections**, find **Linear**, and choose **Connect**. Or ask in Slack, `@pm connect Linear`, and follow the link it posts.
2. Choose who uses it. **Team** is one shared Linear account that everyone who can use the teammate acts through. **Personal** means each member signs in as themselves, and Linear records their actions as them.
3. Choose **Continue to sign in**. Linear asks you to approve read and write access for the workspace you pick. There is no token to paste and no config file to edit.
4. Chickpea connects to [mcp.linear.app/mcp](https://linear.app/docs/mcp) and records the tools the server answered with. The teammate is handed that list, and it can later be narrowed to fewer tools but never widened to more.
5. Ask something. `@pm what is left in the current cycle` is a good first question, because it reads and cannot change anything.

A connection belongs to one teammate. Giving a second teammate Linear means a second sign-in with its own consent, so the support teammate never inherits what the engineering teammate can reach.

## What the teammate is handed with Linear
There is no built-in Chickpea skill for Linear, and none is needed. The tools arrive from Linear's MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Linear describes them as tools for finding, creating, and updating objects such as issues, projects, and comments.

Linear documents the server and the clients it supports: https://linear.app/docs/mcp

## Beside Linear
- **Sentry:** An error in Sentry becomes an issue with the stack trace attached
- **Asana:** Engineering work in Linear, the rest of the company in Asana, one teammate that reads both
- **Zendesk:** A ticket that turns out to be a bug gets filed and linked back
- **PostHog:** Check what the release did before anyone closes the issue
- All 37 connectors: https://chickpea.co/connectors

## Questions people ask

### Is there a Linear MCP?
Yes. Linear runs a hosted MCP server at mcp.linear.app/mcp over streamable HTTP, with OAuth sign-in, and documents setup for Claude, Cursor, VS Code, Codex, and others. Chickpea connects to that same server, so a teammate in Slack uses it without any of those clients installed.

### How do I set up the Linear MCP?
For a coding client, follow Linear's own docs, since each client keeps its own config. For Slack there is nothing to configure. Open the teammate in Chickpea Admin, choose Linear, choose Continue to sign in, and approve the workspace. Or ask "@pm connect Linear" in the channel and follow the link it posts.

### Does it use Linear's MCP server or the API?
The MCP server. Linear is a vendor MCP lane: the deployment connects to mcp.linear.app/mcp over streamable HTTP and signs in with OAuth, asking for read and write. There is no API key anywhere in this connector, and the connection cannot reach any other address.

### Can I use this from Claude Code or Cursor instead?
Yes, and Linear documents both. Those put the server in one person's editor. A teammate puts it in a channel, with a stored connection, saved instructions, schedules, and every action visible in the thread where it was asked for. Teams often run both.

### Do I still need Linear's own Slack integration?
Usually yes. Linear's Slack app sends notifications, unfurls issue links, syncs a Slack thread to a comment thread on the issue, and since October 2025 has an @Linear agent that creates issues from a conversation. A Chickpea teammate hears nothing from Linear and posts nothing unprompted. What it adds is reading across the workspace, changing many issues at once, and schedules, in the same channel as your other connected accounts.

### Which Linear plan does this need?
Linear's MCP documentation names no plan requirement, and Linear says its Slack agent is on all plans. What the teammate can see and change is what the account you signed in with can see and change, because it acts through that sign-in.

### Can it delete issues?
Linear describes the server as tools for finding, creating, and updating issues, projects, and comments, and names no delete tool, so this page will not claim one way or the other about what exists. What is fixed is the gate. During a Slack turn Chickpea refuses any MCP tool whose name does not start with an unambiguous read verb unless your message names that action. Thread history, retrieved content, and memory cannot authorize a write on their own.

### Where does the OAuth token live?
On your deployment, outside the teammate record. It never enters the model's context, the tool arguments the model writes, or Slack. The model picks a connection by id and the credential goes in at the last step on the way out. Disconnect the account and the stored secret is removed, and any schedule that depended on it stops.

### Does everyone act as the same Linear user?
That is your choice when you connect. A team account is one shared sign-in that everyone with access to the teammate acts through. A personal account belongs to one member inside one teammate, so your sign-in is used only for your requests and nobody else's.

### Does Linear integrate with Slack?
Two ways. Linear ships its own Slack app for notifications, issue creation, and synced threads. A Chickpea teammate is the other way: it holds a Linear connection and does what you ask in the channel, through Linear's MCP server. They do different jobs, and both can be installed.

## Sources
- [Chickpea docs: connector catalog, the Linear preset, its lane and OAuth scope](https://docs.chickpea.co/reference/connector-catalog/)
- [Chickpea docs: connections, team and personal accounts, the binding as a ceiling](https://docs.chickpea.co/agents/connections/)
- [Chickpea docs: authority and confirmation, including the read-verb gate](https://docs.chickpea.co/security/authority-and-confirmation/)
- [Chickpea docs: connect a service, OAuth presets and the Slack link](https://docs.chickpea.co/agents/connect-a-service/)
- [Chickpea docs: schedules, time zones and what each run rechecks](https://docs.chickpea.co/agents/schedules/)
- [Chickpea source: the Linear preset (server URL, transport, OAuth scope)](https://github.com/pejmanjohn/chickpea/blob/main/src/config/presets.ts)
- [Chickpea source: an MCP connection exposes approved tools that are still discovered](https://github.com/pejmanjohn/chickpea/blob/main/src/config/types.ts)
- [Linear docs: the MCP server, its URL, OAuth, and supported clients](https://linear.app/docs/mcp)
- [Linear docs: the Slack integration](https://linear.app/docs/slack)
- [Linear changelog: the Linear agent for Slack, October 2025](https://linear.app/changelog/2025-10-23-linear-agent-for-slack)
- [Chickpea source on GitHub](https://github.com/pejmanjohn/chickpea)

## More
- [Ahrefs MCP in Slack](https://chickpea.co/connectors/ahrefs.md)
- [Airtable MCP in Slack](https://chickpea.co/connectors/airtable.md)
- [Asana AI agent in Slack](https://chickpea.co/connectors/asana.md)
- [Jira and Confluence MCP in Slack](https://chickpea.co/connectors/atlassian.md)
- [BugSnag MCP in Slack](https://chickpea.co/connectors/bugsnag.md)
- [Cloudflare MCP in Slack](https://chickpea.co/connectors/cloudflare-api.md)
- [Exa MCP in Slack](https://chickpea.co/connectors/exa.md)
- [Firecrawl MCP in Slack](https://chickpea.co/connectors/firecrawl.md)
- [Fireflies MCP in Slack](https://chickpea.co/connectors/fireflies.md)
- [Gamma MCP in Slack](https://chickpea.co/connectors/gamma.md)
- [Gmail AI agent in Slack](https://chickpea.co/connectors/gmail.md)
- [Gong AI agent in Slack](https://chickpea.co/connectors/gong-managed.md)
- [Google Ads AI agent in Slack](https://chickpea.co/connectors/google-ads.md)
- [Google Analytics AI agent in Slack](https://chickpea.co/connectors/google-analytics.md)
- [Google Calendar AI agent in Slack](https://chickpea.co/connectors/google-calendar.md)
- [Google Docs AI agent in Slack](https://chickpea.co/connectors/google-docs.md)
- [Google Drive AI agent in Slack](https://chickpea.co/connectors/google-drive.md)
- [Google Search Console AI agent in Slack](https://chickpea.co/connectors/google-search-console.md)
- [Google Sheets AI agent in Slack](https://chickpea.co/connectors/google-sheets.md)
- [Google Slides AI agent in Slack](https://chickpea.co/connectors/google-slides.md)
- [Granola MCP in Slack](https://chickpea.co/connectors/granola.md)
- [HubSpot AI agent in Slack](https://chickpea.co/connectors/hubspot-managed.md)
- [Hugging Face MCP in Slack](https://chickpea.co/connectors/huggingface.md)
- [incident.io MCP in Slack](https://chickpea.co/connectors/incident-io.md)
- [Intercom MCP in Slack](https://chickpea.co/connectors/intercom.md)
- [LunarCrush MCP in Slack](https://chickpea.co/connectors/lunarcrush.md)
- [Meta Ads MCP in Slack](https://chickpea.co/connectors/meta-ads.md)
- [Monday.com MCP in Slack](https://chickpea.co/connectors/monday.md)
- [Neon MCP in Slack](https://chickpea.co/connectors/neon.md)
- [Notion Slack integration with an AI agent](https://chickpea.co/connectors/notion-managed.md)
- [PostHog MCP in Slack](https://chickpea.co/connectors/posthog.md)
- [Sentry MCP in Slack](https://chickpea.co/connectors/sentry.md)
- [Stripe MCP in Slack](https://chickpea.co/connectors/stripe.md)
- [Supabase MCP in Slack](https://chickpea.co/connectors/supabase.md)
- [YouTube AI agent in Slack](https://chickpea.co/connectors/youtube-managed.md)
- [Zendesk AI agent in Slack](https://chickpea.co/connectors/zendesk.md)
- [All connectors](https://chickpea.co/connectors.md)

## Try Chickpea
- Site: https://chickpea.co/
- Deploy to Cloudflare: https://deploy.workers.cloudflare.com/?url=https://github.com/pejmanjohn/chickpea
- Source, Apache 2.0: https://github.com/pejmanjohn/chickpea
- Docs: https://docs.chickpea.co