# How to connect Jira to OpenClaw > Connect Jira to OpenClaw in one click. 10 Jira tools your agent can call from chat. No API keys. Web version: https://claw-link.dev/openclaw/jira ClawLink gives OpenClaw a more practical Jira setup than rolling your own integration. Install one ClawHub skill, connect Jira in the browser, and OpenClaw can call real Jira actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Jira MCP for OpenClaw Looking for a Jira MCP server for OpenClaw? ClawLink connects Jira to OpenClaw and exposes 10 Jira tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Jira integration](https://claw-link.dev/hermes/jira) works the same way. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/jira ## Setup It takes three steps to connect OpenClaw to Jira. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Jira** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect jira # connect Jira (browser OAuth) npx -y @useclawlink/cli actions jira # list available actions npx -y @useclawlink/cli run jira --input '' # execute (add --confirm for writes) ``` ## What the OpenClaw Jira integration can do 10 Jira tools are ready for OpenClaw once the account is connected. ### All 10 Jira tools for OpenClaw | Tool | What it does | |---|---| | **Fetch bulk issues** `jira_fetch_bulk_issues` | Bulk fetch multiple Jira issues by IDs or keys | | **Find users2** `jira_find_users2` | Find users in Jira by query or account ID | | **Get all groups** `jira_get_all_groups` | Retrieve all groups from the Jira instance | | **Check permissions** `jira_check_permissions` | Check user permissions for Jira operations | | **Add attachment** `jira_add_attachment` | Upload and attach a file to a Jira issue | | **Add comment** `jira_add_comment` | Add a comment to an existing Jira issue | | **Add users to project role** `jira_add_users_to_project_role` | Add users to a Jira project role | | **Add user to group** `jira_add_user_to_group` | Add a user to a Jira group | | **Create jql autocompletedata** `jira_create_jql_autocompletedata` | Retrieve JQL autocomplete reference data | | **Evaluate jira expression** `jira_evaluate_jira_expression` | Evaluate Jira expressions using the enhanced search API | ## Example prompts **Fetch Bulk Issues** > Pull the relevant data from Jira, summarize it in plain English, and point out anything that needs attention. **Find Users2** > Use Jira to find users2 and walk me through the result in plain English. **Get All Groups** > Pull the relevant data from Jira, summarize it in plain English, and point out anything that needs attention. **Check Permissions** > Use Jira to check permissions and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Jira working from chat. | | Manual | ClawLink | |---|---|---| | **Connection flow** | Register a Jira app, configure redirect URLs, manage consent details, and reconnect users when auth settings drift. | Users connect Jira through the hosted browser flow and ClawLink keeps the token lifecycle out of your app code. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Jira. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Jira actions to the runtime in a format your agent can reliably use. | 10 tools for Jira are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Jira to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Jira in the browser, and the 10 tools above work from chat. There is no SDK, no config file, and no API key handling. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Jira skill but can't call the tools The ClawHub skill teaches OpenClaw about Jira, but the calls run through the ClawLink plugin and your connected account. Make sure Jira is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Jira from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### The Jira account is connected but the action fails Check whether the connected account has access to the workspace, inbox, store, or project you are trying to use. Most failures at this stage are permission mismatches, not ClawLink bugs. ### OAuth finished in the browser but the account is still missing Try reconnecting Jira and complete the consent flow in the same browser session. Partial OAuth approvals or switching accounts mid-flow can leave the connection incomplete. ### Is there a OpenClaw Jira integration? Yes. ClawLink is the fastest way to connect OpenClaw to Jira: link your Jira account once in the browser and OpenClaw can call the Jira API through 10 ready-made tools — no custom code or token handling. ### How do I add Jira to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Jira skill from ClawHub, then you click Connect in the dashboard to authorize Jira. OpenClaw calls the tools from the next message — no config files or API keys. ### How long does it take to connect Jira to OpenClaw? About two minutes. Sign in, click Connect next to Jira in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Jira up myself? The alternative to ClawLink is usually manual OAuth app setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Jira working from chat. ### OpenClaw installed the Jira skill but can't call the tools The ClawHub skill teaches OpenClaw about Jira, but the calls run through the ClawLink plugin and your connected account. Make sure Jira is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Apify tools](https://claw-link.dev/openclaw/apify) — Run web scrapers, manage Actors, datasets, and schedules - [OpenClaw Hostinger integration](https://claw-link.dev/openclaw/hostinger) — Manage domains, DNS, VPS, and web hosting - [Vercel tools](https://claw-link.dev/openclaw/vercel) — Manage projects, deployments, domains, and environment variables