Connector · Project management
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.
What people ask it.
The teammate is @pm, in #eng. Pick a scenario to watch it play.
File an issue Applies at once
@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 Read only
@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 Asks first
@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 Applies at once
@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 Applies at once
@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.
Connect it
Five steps, from Admin or from Slack.
You sign in through a page Chickpea serves, never in Slack. The link the teammate posts is good for one action, for one teammate, for 24 hours.
- 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. - 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.
- 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.
- Chickpea connects to mcp.linear.app/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.
- Ask something.
@pm what is left in the current cycleis 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.
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.
Beside Linear
What the same teammate usually holds too.
Each is its own connection, granted to the teammate alone. All 37 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.
Try it
Give a channel a Linear teammate.
One deploy into your own Cloudflare account, connect Slack, sign in to Linear, ask. Apache 2.0, no seats, no metering.
Or run it on Node. The setup guide covers both.
Last checked
Facts on this page were checked against the product and Linear's own pages on September 17, 2026. This page is also available as markdown at /connectors/linear.md.