oshaani MCP Marketplace
Sign in

← Documentation

Jira MCP Work tracking

Search issues with JQL, read details and comments, and create, comment on and transition issues in Jira.

1 credits / tool call

Quick start

  1. Add a Jira connection with the settings below, then click Test configuration.
  2. Create an API key for your agent.
  3. Paste the key below, click Test endpoint, and copy the configuration for your platform.
Endpointhttps://market.oshaani.com/jira (your default connection) or https://market.oshaani.com/jira/<connection-id>
TransportStreamable HTTP (stateless, JSON responses). MCP protocol versions 2024-11-05 to 2025-11-25 and 2026-07-28.
AuthenticationAuthorization: Bearer <API key>, using a key from the API keys page.

Agent configuration

The default URL uses your organisation's default Jira connection; a URL with an ID pins one connection.
Get a key
The key is filled into the snippets below. It stays in this page and is only sent with the test request.
Runs initialize and tools/list against the endpoint, exactly like an agent. No credits are charged.

Any MCP client that supports remote (Streamable HTTP) servers with custom headers.

{
  "name": "jira",
  "transport": "streamable-http",
  "url": "https://market.oshaani.com/jira",
  "headers": {
    "Authorization": "Bearer YOUR_API_KEY"
  }
}

Connection settings

Entered once per connection on market.oshaani.com. Secrets are encrypted and never shown again or sent to agents.

SettingTypeDescription
Jira URL
url required
string (uri) e.g. https://your-company.atlassian.net or your Data Center URL
min length 1, max length 2083
Deployment
deployment
"cloud" | "data_center"
default "cloud"
Jira Cloud or Jira Data Center/Server
Account email
email
string Jira Cloud only: the email of the account that owns the API token
API token
api_token required secret
string Jira Cloud: create at id.atlassian.com > Security > API tokens. Data Center: a personal access token.
Verify TLS certificate
verify_tls
boolean
default true
Allow creating, commenting on and transitioning issues
allow_write_actions
boolean
default false
Off by default: agents can only read data until this is enabled

Tools (7)

search_issues read-only

Search issues with JQL

ArgumentTypeDescription
jql required string e.g. 'project = OPS AND assignee = currentUser() ORDER BY updated DESC'
min length 1
max_results integer
default 25

min 1, max 100
page_token string next_page_token from a previous call, to get the next page

get_issue read-only

Get an issue with its description, sub-tasks, links and recent comments

ArgumentTypeDescription
key required string Issue key, e.g. OPS-123
pattern ^[A-Za-z][A-Za-z0-9_]*-\d+$
max_comments integer
default 10

min 0, max 50

list_projects read-only

List projects visible to the account

ArgumentTypeDescription
query string Filter by project name or key

get_transitions read-only

List the status transitions currently available for an issue

ArgumentTypeDescription
key required string Issue key, e.g. OPS-123
pattern ^[A-Za-z][A-Za-z0-9_]*-\d+$

create_issue

Create an issue

ArgumentTypeDescription
project_key required string
pattern ^[A-Za-z][A-Za-z0-9_]*$
summary required string
min length 1, max length 255
issue_type string
default "Task"
e.g. Task, Bug, Story
description string Plain text or Jira wiki markup
priority string e.g. High, Medium, Low
labels array of string

add_comment

Add a comment to an issue

ArgumentTypeDescription
key required string Issue key, e.g. OPS-123
pattern ^[A-Za-z][A-Za-z0-9_]*-\d+$
body required string Plain text or Jira wiki markup
min length 1, max length 32000

transition_issue

Move an issue to another status using a transition from get_transitions

ArgumentTypeDescription
key required string Issue key, e.g. OPS-123
pattern ^[A-Za-z][A-Za-z0-9_]*-\d+$
transition required string Transition ID or name, e.g. 'Done' or '31'
min length 1
comment string

Billing & errors

Each successful tool call costs 1 oshaani.com credit. initialize, tools/list, failed calls and timeouts are free.

JSON-RPC codeMeaning
-32054 (HTTP 401)Missing, unknown or revoked API key
-32053 (HTTP 404)No Jira connection configured for your organisation, or the connection ID is wrong
-32055 (HTTP 403)Connection disabled or origin not allowed
-32052 (HTTP 429)Rate limit reached; retry after a minute
-32050Not enough oshaani.com credits for the call
-32051Billing temporarily unavailable; the call was not run

Errors from Jira itself (bad IDs, permissions) come back as tool results with isError: true so the agent can read and correct them. See the Jira API documentation.