Jira is one of the most requested integrations for teams using OpenClaw — the ability to ask your Slack bot about ticket status, sprint health, or blocked work without opening Jira is genuinely useful. Here's how to wire it up.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Jira — it's considerably more involved.
Connecting OpenClaw with Jira: Step by Step
Step 1: Create an Atlassian API Token
Go to id.atlassian.com/manage-profile/security/api-tokens and generate a token. The Jira Cloud REST API uses basic authentication with your email address and this token. Your Jira base URL will be https://yourcompany.atlassian.net.
Step 2: Explore the API and Pick Your Endpoints
The Jira REST API (/rest/api/3/) has endpoints for issues, projects, sprints (via the Agile API at /rest/agile/1.0/), and users. Decide which queries your team will actually use and build your proxy around those — don't try to expose everything at once.
Step 3: Build the Proxy and Skill File
Build a proxy that wraps your most-needed Jira queries and write ~/.openclaw/skills/jira.md. Include your project keys (e.g., PROJ, ENG) in the skill file so Claude knows how to construct issue identifiers from natural-language questions.
Challenges and Caveats
Jira Server vs Jira Cloud Have Different APIs
If you're on Jira Server or Data Center (self-hosted), the authentication mechanism and some endpoints differ from Jira Cloud. Personal access tokens work for Server/DC, but basic auth with Atlassian tokens is Cloud-specific. Make sure you're reading the right docs.
JQL Complexity
Jira's query language (JQL) is powerful but has a learning curve. Your proxy or skill file will need to translate natural-language queries into JQL. Claude can help generate JQL, but it will sometimes get the syntax wrong — test thoroughly.
Sprint Data Requires the Agile API
Sprint and board information is in a separate API (/rest/agile/1.0/) and requires different permissions. If sprint queries are important to you, make sure your API token has access to the Agile project.
Skip All of This — Use Cody Instead
Cody includes Jira integration out of the box. Ask about tickets, sprints, and blockers directly in Slack without any configuration.
Related Guides
- Connecting OpenClaw with Linear: A Practical Guide
- Connecting OpenClaw with Github: A Practical Guide
- Connecting OpenClaw with Notion: A Practical Guide
Need the model-flexible version? See: How to Connect Jira to OpenClaw: Setup, Models, and Workflow Guide.