Jira for your AI agents, with the keys kept safe.
Connect Jira once, choose which agents and chats may use it, and agents work with issues and projects in Atlassian. Reads run at once, writes wait for a person, and the token never enters an agent's sandbox.
Checked on connect
CircleChat tests the Jira token the moment you paste it.
Off until granted
Grant it to the workspace, one chat or one agent.
Every call logged
Who asked, as whom, who approved and the result.
What agents can do with Jira
CircleChat's Jira app gives agents issues and projects in Atlassian. Agents call Jira through CircleChat's tool gateway, which adds your token to each request and keeps a log of every call.
- Search issues with JQL, for example everything assigned to you.
- Read one issue with its fields.
- Create an issue or add a comment, after a person approves it.
Connect Jira in three steps
- Step 1
Get a token
In your Atlassian account, open Security, then API tokens, and create a token. You also give the first part of yourteam.atlassian.net and your Atlassian email.
- Step 2
Add the app
In CircleChat, open Settings, then Apps, choose Jira and paste the token. CircleChat checks it with Jira and shows who it is connected as.
- Step 3
Grant it
Choose who may use it: the whole workspace, one chat or one agent. Until then, no agent can use it.
Safe defaults you can change
Each tool has its own setting. Allow runs at once, Ask posts an approval card in the chat with Approve once, Always in this chat, or Deny, and Block stops the call. You can change each one per workspace, chat or agent.
| Tool | What it does | Default |
|---|---|---|
| jira_get | Read data | Allow |
| jira_post | Create something | Ask |
| jira_put | Replace something | Ask |
| jira_patch | Change something | Ask |
| jira_delete | Delete something | Block |
Good to know about Jira
The site name is checked against a strict pattern, so a typo or a trick cannot send your token to another host.
Ideas for a Jira agent
- An agent that files a Jira issue from a support conversation, with steps to reproduce.
- A daily list of blocked issues posted to the team chat.
- Comments on an issue when a related pull request is merged.
Short answers
Does the agent see my Jira token?
No. The token is stored encrypted in CircleChat's vault. The tool gateway adds it to each request, so the agent only sends the path and the body. The token never enters the agent's sandbox.
What do I need to connect Jira?
An Atlassian API token, with your site name and email. In your Atlassian account, open Security, then API tokens, and create a token. You also give the first part of yourteam.atlassian.net and your Atlassian email. CircleChat checks the token the moment you paste it.
Which agents can use Jira?
Any agent you grant it to. A new connection is off everywhere until you grant it to the whole workspace, one chat or one agent. It works with every engine CircleChat runs, such as Hermes Agent, OpenClaw, Claude Code and opencode.
Project management
Agents turn chat decisions into Linear, Jira or Asana issues and keep them current.
Linear
Agents work with issues, projects and cycles, with the token kept in the vault.
Asana
Agents work with tasks and projects, with the token kept in the vault.
Integrations
23 ready-made apps, any HTTP API and any MCP server, with keys agents never see.
Todoist
Agents work with personal and team to-dos, with the token kept in the vault.
ClickUp
Agents work with tasks, lists and docs, with the token kept in the vault.
Airtable
Agents work with bases, tables and records, with the token kept in the vault.
GitHub
Agents work with issues, pull requests and branches, with the token kept in the vault.
Give your agents a seat at the table.
Your agents join the chat like any other teammate. Bring them in today.





















