# Connect Jira to your AI agent

> Yes — ClawLink is a hosted Jira MCP server. 94 tools your agent can call from chat, with one-click hosted OAuth and nothing to run locally.

Web version: https://claw-link.dev/hub/jira

ClawLink hosts a managed Jira MCP server that exposes 94 tools to your AI agent. You connect Jira in one click, and your agent can read, create, and update Jira data from chat without you building or running a local MCP server.

## Quick facts

- 94 tools callable from chat
- One-click hosted OAuth
- Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any MCP client
- No local server or config files

## Overview

The usual path is: build auth, handle token refresh, wire up the tools. With ClawLink you connect Jira once and start using the real actions from the agent.

## Setup

Jira uses OAuth. You connect it in the browser: click Connect, sign in, approve. ClawLink stores the token and refreshes it on its own. You never touch a key or wire up a redirect URL.

Authentication: hosted OAuth

## What you can do

- **Work without tab-switching** — Pull up Jira issues, repos, tasks, or alerts without leaving the conversation.
- **Ship the routine stuff faster** — The agent grabs Jira context, drafts the next step, and runs the common maintenance actions.
- **Debug with real data** — Ask for the current state from Jira before the agent suggests a fix. No guessing.

## Jira tools

94 Jira tools, ready the moment you connect.

- `jira_add_attachment` — Upload and attach a file to a Jira issue
- `jira_add_comment` — Add a comment to an existing Jira issue
- `jira_add_user_to_group` — Add a user to a Jira group
- `jira_add_users_to_project_role` — Add users to a Jira project role
- `jira_check_permissions` — Check user permissions for Jira operations
- `jira_create_jql_autocompletedata` — Retrieve JQL autocomplete reference data
- `jira_evaluate_jira_expression` — Evaluate Jira expressions using the enhanced search API
- `jira_fetch_bulk_issues` — Bulk fetch multiple Jira issues by IDs or keys
- `jira_find_users2` — Find users in Jira by query or account ID
- `jira_get_all_groups` — Retrieve all groups from the Jira instance
- `jira_analyse_expression` — Analyses Jira expressions for syntax validation, type checking, and complexity analysis
- `jira_find_users_for_picker` — Find users for picker components by matching query against user attributes like display name
- `jira_get_all_issue_type_schemes` — Retrieves all Jira issue type schemes with optional filtering and pagination
- `jira_get_all_projects` — Retrieves all visible projects using the modern paginated Jira API with server-side filtering
- `jira_get_all_statuses` — Retrieves all issue statuses associated with workflows from Jira
- `jira_get_all_users` — Retrieves all users from the Jira instance including active, inactive, app accounts, and system
- `jira_get_attachment` — Retrieves the binary content of a Jira attachment by ID
- `jira_get_attachment_meta` — Retrieve Jira attachment settings including upload limits and enabled status
- `jira_get_comment` — Retrieves a specific comment by ID from a Jira issue with optional expansions
- `jira_get_components` — Retrieve components from Jira projects with search and filtering
- `jira_get_create_metadata_issue_type_fields` — Retrieve field metadata for a specific issue type in a project
- `jira_get_current_user` — Retrieves detailed information about the currently authenticated Jira user
- `jira_get_dashboards` — List and search Jira dashboards visible to the current user
- `jira_get_favorite_filters` — Retrieve favorite filters for the current user
- `jira_get_fields` — Retrieve Jira issue fields metadata
- `jira_get_fields_paginated` — Retrieve Jira fields in pages
- `jira_get_filter` — Retrieves a specific Jira saved filter by ID, including its JQL and sharing metadata, to reuse
- `jira_get_group` — Retrieves details of a specific Jira group by name or ID
- `jira_get_info` — Retrieves runtime information for the Jira Service Management instance
- `jira_get_issue` — Retrieves a Jira issue by ID or key with customizable fields and expansions

## Example prompts

- **Add attachment:** Use Jira to add attachment and walk me through it.
- **Add comment:** Use Jira to add comment and walk me through it.
- **Add user to group:** Use Jira to add user to group and walk me through it.
- **Add users to project role:** Use Jira to add users to project role and walk me through it.

## ClawLink vs. building it yourself

| | Manual | ClawLink |
|---|---|---|
| Connection | Build it yourself. You register a developer app with Jira, set up redirect URLs, handle the consent screen, store and refresh access tokens, and redo the wiring when scopes change. | Hosted hosted OAuth. Connect once in the browser. ClawLink owns the lifecycle. |
| Maintenance | Token refresh, permission debugging, env config, every edge case. All yours. | ClawLink handles the plumbing. You focus on the workflow. |
| Time to first call | Days to weeks. Auth, storage, tool wiring, testing. Then the agent can act. | About two minutes from sign-up to the agent calling Jira. |

## FAQ

### How do I connect Jira to my AI agent?

Install ClawLink, open the dashboard, click Connect next to Jira, and finish the hosted OAuth flow. Your agent can call Jira from the next message. Two minutes, total.

### Is there a Jira MCP server I can use?

Yes. ClawLink exposes Jira as 94 tools your agent calls through a hosted MCP-compatible runtime. You don't run a local server or edit a config file. The tools are there the moment you connect.

### Do I need Jira API credentials?

No separate API key. You sign in to Jira through the normal OAuth flow and ClawLink handles the token after that.

### How much does it cost?

Your first integration is free, plus a 7-day trial of the full catalog. Paid plans unlock the rest of the library.

### Can I set this up from the terminal instead of the dashboard?

Yes. Run npx -y @useclawlink/cli login, then npx -y @useclawlink/cli connect jira. The first opens a browser to sign in to ClawLink. The second opens a browser to authorize Jira. No API keys to create. Works with OpenClaw, Hermes, Claude Code, Cursor, Codex, and any agent that runs shell commands.