Developer toolsPublic source

Jira MCP Server

Give your AI agents full Jira access — issues, projects, sprints, boards, comments, transitions, and JQL search. 15 tools over the Jira Cloud REST API v3 with enterprise governance.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides jira capabilities through a typed MCP contract.

Architecture

How Jira MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Jira MCP Server

Validates the request and owns 15 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Jira MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Jira MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

15 named tools

list_projects

List all Jira projects

read only

get_project

Get project details by key

read only

search_issues

Search issues using JQL

read only

get_issue

Get issue details by key

read only

create_issue

Create a new issue (Story, Bug, Task, or Epic)

internal write

update_issue

Update issue fields (summary, description, priority, labels)

internal write

transition_issue

Transition an issue through workflow states

internal write

assign_issue

Assign an issue to a user

internal write

add_comment

Add a comment to an issue

internal write

list_comments

List comments on an issue

read only

get_transitions

Get available workflow transitions for an issue

read only

list_sprints

List sprints for a board

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

8 read only7 internal write

The registry manifest declares read only, internal write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-jira

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-jira",
    ["mcp-jira"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring