Connector · Project management
A Jira and Confluence teammate in Slack, on Atlassian's MCP server.
Chickpea gives a channel a named AI teammate that holds its own Atlassian connection. It signs in with OAuth and calls Atlassian's MCP server, so there is no client to configure and no token to paste. Ask it in Slack to file a Jira issue, read the sprint, or find the Confluence page that answers a question. It replies in the thread.
What people ask it.
The teammate is @pm, in #eng. Pick a scenario to watch it play.
File an issue from a thread Applies at once
@pm file this thread in Jira: checkout retries a 402 and charges twice. Payments project, bug, high
@pm create a Jira issue for the refund webhook loop and assign it to Marco
A new issue is a small, reversible write, so it goes straight through. The reply names the key, the project, and the priority it set, with a link into Jira. Anything you leave out it asks about rather than guessing.
Read the sprint Read only
@pm what is left in the current sprint, and is anything blocked
@pm show me every high-priority bug in Payments that nobody owns
Reads never need confirmation, and a long answer comes back as a table in the thread. Atlassian gives the server JQL search plus board and sprint data, so a question about the sprint is answered from Jira rather than guessed.
Transition and reassign Asks first
@pm move PAY-214 to In Review and put Priya on it
@pm everything in the Payments backlog about refunds goes to Marco, into this sprint
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.
Find a Confluence page Read only
@pm what does our runbook say about replaying a failed payment
@pm find the Confluence page on the refund policy and summarize it here
The server searches Confluence and reads page content, so the teammate quotes the page instead of paraphrasing from memory. What it can see is what the signed-in Atlassian account can see; connecting does not widen anyone.
On a schedule Applies at once
@pm every Friday at 4pm Eastern, list what slipped out of the sprint
@pm every weekday at 9am Pacific, post the unassigned bugs in Payments
A schedule saves on the spot. It needs an explicit time zone, runs under the Atlassian 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 Atlassian, and choose Connect. Or ask in Slack,
@pm connect Atlassian, and follow the link it posts. - Choose who uses it. Team is one shared Atlassian account that everyone who can use the teammate acts through. Personal means each member signs in as themselves, and Atlassian records their actions as them.
- Choose Continue to sign in. Atlassian's consent screen is where you pick the sites and products this connection reaches, so a teammate can be pointed at one Jira site and left out of the rest.
- Chickpea connects to mcp.atlassian.com 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 sprintis a good first question, because it reads and cannot change anything.
Chickpea asks for read and write across Jira and Confluence, plus Compass and Teamwork Graph scopes. That request is a ceiling. Atlassian says every action runs inside the permissions of the signed-in user, and an organization admin can turn tools off for everyone. A connection also belongs to one teammate, so the support teammate never inherits what the engineering teammate can reach.
There is no built-in Chickpea skill for Atlassian, and none is needed. The tools arrive from Atlassian's MCP server: Chickpea connects before it saves anything, records what the server answered with, and exposes only those tools. Atlassian's list covers reading, searching, creating, and updating Jira issues, boards, sprints, and comments, and Confluence pages, spaces, and comments. Atlassian publishes the full tool list.
Beside Atlassian
What the same teammate usually holds too.
Each is its own connection, granted to the teammate alone. All 37 connectors.
An error in Sentry becomes a Jira issue with the stack trace attached
ZendeskA ticket that turns out to be a bug gets filed in Jira and linked back
LinearEngineering work in Linear, the rest of the company in Jira, one teammate that reads both
Google DriveThe spec lives in Drive, the work item lives in Jira, one ask covers both
Questions people ask
Does Atlassian have an MCP?
Yes. Atlassian runs a hosted server called the Atlassian Rovo MCP Server at mcp.atlassian.com, over streamable HTTP with OAuth. Atlassian documents setup for Claude, Claude Code, Cursor, VS Code, ChatGPT, Codex, Gemini, and others. Chickpea connects to that same server, so a teammate in Slack uses it without any of those clients installed.
Is Jira MCP free?
Atlassian says access to the MCP server is available to all Atlassian Cloud customers, and publishes a call limit per site: 500 an hour on Free, 1,000 an hour on Standard, and 1,000 an hour on Premium and Enterprise plus 20 more per user, up to 10,000. Atlassian also says some tools consume Rovo credits, and names Teamwork Graph and Rovo Search calls at up to 10 credits each. Chickpea adds no fee of its own; you run it on your Cloudflare account.
Does it work with Jira Data Center or only Cloud?
Atlassian documents the Rovo MCP Server under Cloud and names no Data Center or Server support, so this connector is for Jira Cloud and Confluence Cloud. Atlassian also says the server does not currently meet FedRAMP or HIPAA requirements. If your Jira is self-hosted, this preset has nothing to connect to.
Does it use Atlassian's MCP server or the API?
The MCP server. Atlassian is a vendor MCP lane: the deployment connects to mcp.atlassian.com over streamable HTTP and signs in with OAuth. There is no Jira API token anywhere in this connector, no base URL to set, and the connection cannot reach any other address.
Is this Rovo?
It uses the server Rovo publishes, and it is not Rovo. Atlassian describes Rovo as its own AI, covering search, chat, studio, and agents inside Atlassian products. It describes the Rovo MCP Server as an integration layer that connects other AI clients to Atlassian data, not a model. Chickpea is one of those clients, running in Slack on your own infrastructure.
Can it delete issues or pages?
Atlassian's tool list does include delete tools for Jira issues, comments, and attachments, and says they are disabled by default until an admin turns them on. On top of that sits Chickpea's own 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 or a delete 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.
Do I still need Jira Cloud for Slack?
Usually yes. Atlassian's own Slack app sends notifications to your DMs, turns a pasted issue key into an editable card, creates and updates work items from a message, and syncs a Slack thread into comments on a work item. A Chickpea teammate hears nothing from Jira and posts nothing unprompted. What it adds is reading across Jira and Confluence in one ask, changing many issues at once, saved instructions, schedules, and your other connected accounts in the same channel. The two run side by side.
How do I sync a Slack thread with Jira?
That one is Atlassian's. Jira Cloud for Slack has a thread sync that keeps a Slack thread and a work item's comments in step, and it is worth installing for that alone. A Chickpea teammate does the adjacent job: ask it to file the thread and it writes the discussion into the issue description, once, with a link back.
Can I use this from Claude Code, Cursor, or VS Code instead?
Yes, and Atlassian documents all three. 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.
Try it
Give a channel an Atlassian teammate.
One deploy into your own Cloudflare account, connect Slack, sign in to Atlassian, 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 Atlassian's own pages on September 17, 2026. This page is also available as markdown at /connectors/atlassian.md.