Which integrations are available for this server?

Provides tools for searching, retrieving, and interacting with JIRA issues, including semantic search, issue details, user issues, and connection testing, enabling AI agents to manage JIRA tasks programmatically.

How do I use JIRA MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@JIRA MCP Server show my open bugs in project PROJ" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

JIRA MCP Server

by wunderfrucht

Overview Schema Related Servers Score Discussions

Rust

Remote

JIRA MCP Server

An AI-friendly JIRA integration server using the Model Context Protocol (MCP). This server provides semantic tools for searching, retrieving, and interacting with JIRA issues without requiring knowledge of JQL or JIRA internals.

✨ Features

🤖 AI-Friendly Interface: Uses semantic parameters instead of JQL
🔄 Automatic JIRA Detection: Leverages gouqi 0.14.0 for Cloud/Server detection
⚡ Smart Caching: Metadata caching with TTL for performance
🛠️ Comprehensive Tools: Search, issue details, user issues
🚦 Error Handling: MCP-compliant error codes and messages
🔐 Flexible Authentication: Supports PAT, Basic, Bearer, and Anonymous auth

Related MCP server: Jira MCP Server

🚀 Quick Start

Prerequisites

Rust 1.75.0 or later
Access to a JIRA instance (Cloud or Server)
JIRA authentication credentials

1. Configuration

Set up your JIRA connection using environment variables:

# Required: JIRA instance URL
export JIRA_URL="https://your-company.atlassian.net"

# Required: Authentication
export JIRA_AUTH_TYPE="pat"  # or "basic", "bearer", "anonymous"
export JIRA_TOKEN="your_personal_access_token"

# Optional: Advanced settings
export JIRA_CACHE_TTL="300"        # Cache TTL in seconds (default: 300)
export JIRA_MAX_RESULTS="50"       # Max search results (default: 50, max: 200)
export JIRA_REQUEST_TIMEOUT="30"   # Request timeout in seconds (default: 30)

2. Build and Run

# Clone and build
git clone https://github.com/yourusername/gouqi-mcp-server.git
cd gouqi-mcp-server
cargo build --release

# Run the server
./target/release/jira-mcp-server

3. Test Connection

# Test tools
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | ./target/debug/jira-mcp-server

# Test connection
echo '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"test_connection","arguments":{}}}' | ./target/debug/jira-mcp-server

🛠️ Available Tools

`search_issues`

Search for JIRA issues using AI-friendly semantic parameters.

Example Usage:

{
  "issue_types": ["story", "bug"],
  "assigned_to": "me",
  "status": ["open", "in_progress"],
  "project_key": "PROJ",
  "created_after": "7 days ago",
  "limit": 25
}

`get_issue_details`

Get detailed information about a specific JIRA issue.

Example Usage:

{
  "issue_key": "PROJ-123",
  "include_comments": true,
  "include_attachments": true
}

`get_user_issues`

Get issues assigned to a specific user with filtering options.

Example Usage:

{
  "username": "me",
  "status_filter": ["open", "in_progress"],
  "issue_types": ["story", "bug"],
  "due_date_filter": "overdue"
}

`get_server_status`

Get server status and JIRA connection information.

`test_connection`

Test JIRA connection and authentication.

`clear_cache`

Clear all cached metadata.

📁 Project Structure

jira-mcp-server/
├── Cargo.toml                    # Package configuration
├── src/
│   ├── main.rs                   # Server entry point
│   ├── lib.rs                    # Main server implementation
│   ├── config.rs                 # Configuration management
│   ├── cache.rs                  # Metadata caching
│   ├── jira_client.rs            # JIRA API wrapper
│   ├── semantic_mapping.rs       # AI-friendly parameter mapping
│   ├── error.rs                  # Error types and handling
│   └── tools/                    # MCP tool implementations
│       ├── mod.rs
│       ├── search_issues.rs
│       ├── issue_details.rs
│       └── user_issues.rs
├── config/
│   └── jira-mcp-config.toml.example  # Configuration example
└── README.md

⚙️ Configuration

Environment Variables (Recommended)

# Required
JIRA_URL="https://your-instance.atlassian.net"
JIRA_AUTH_TYPE="pat"  # "pat", "basic", "bearer", "anonymous"
JIRA_TOKEN="your_token"

# For Basic Auth
JIRA_USERNAME="your_username"
JIRA_PASSWORD="your_password"  # pragma: allowlist secret

# Optional
JIRA_CACHE_TTL="300"
JIRA_MAX_RESULTS="50"
JIRA_REQUEST_TIMEOUT="30"
JIRA_RATE_LIMIT="60"

TOML Configuration File (Alternative)

Copy config/jira-mcp-config.toml.example to jira-mcp-config.toml and customize:

jira_url = "https://your-company.atlassian.net"
cache_ttl_seconds = 300
max_search_results = 50

[auth]
type = "personal_access_token"
token = "your_token_here"

[issue_type_mappings]
story = ["Story", "User Story"]
bug = ["Bug", "Defect"]
feature = ["Feature", "Enhancement"]

🔌 Integration with MCP Clients

Claude Desktop

Add to your MCP configuration:

{
  "servers": {
    "jira": {
      "command": "/path/to/jira-mcp-server",
      "env": {
        "JIRA_URL": "https://your-company.atlassian.net",
        "JIRA_AUTH_TYPE": "pat",
        "JIRA_TOKEN": "your_token"
      }
    }
  }
}

Continue.dev

{
  "mcpServers": {
    "jira": {
      "command": "/path/to/jira-mcp-server",
      "env": {
        "JIRA_URL": "https://your-company.atlassian.net",
        "JIRA_AUTH_TYPE": "pat",
        "JIRA_TOKEN": "your_token"
      }
    }
  }
}

🎯 Semantic Parameters

The server translates AI-friendly parameters to JIRA concepts:

Issue Types

"story" → Story, User Story
"bug" → Bug, Defect
"feature" → Feature, Enhancement
"task" → Task, Sub-task
"capability" → Capability, Epic

Status Categories

"open" → Open, To Do, Backlog, New
"in_progress" → In Progress, In Development, In Review
"done" → Done, Closed, Resolved, Complete
"blocked" → Blocked, On Hold, Waiting

User References

"me" or "current_user" → Authenticated user
"unassigned" → Unassigned issues
Any username or account ID

🔧 Development

Building

cargo build

Running with Debug Logs

RUST_LOG=debug cargo run

Testing with MCP Inspector

# Install MCP Inspector
npm install -g @modelcontextprotocol/inspector

# Test your server
npx @modelcontextprotocol/inspector ./target/debug/jira-mcp-server

Running Tests

cargo test

🌟 Example AI Interactions

Find my open stories:

AI: "Show me all the stories assigned to me that are currently open or in progress"
→ Uses: search_issues with {"issue_types": ["story"], "assigned_to": "me", "status": ["open", "in_progress"]}

Get issue details:

AI: "What's the current status and description of PROJ-123?"
→ Uses: get_issue_details with {"issue_key": "PROJ-123"}

Find overdue bugs:

AI: "Show me all bugs that are overdue"
→ Uses: search_issues with {"issue_types": ["bug"], "created_after": "30 days ago", "status": ["open", "in_progress"]}

🚨 Troubleshooting

Connection Issues

Verify JIRA_URL is correct and accessible
Check authentication credentials
Test with test_connection tool
Check firewall/network restrictions

Authentication Issues

Jira Cloud: Use Personal Access Token (PAT)
Jira Server: Use username/password or API token
Verify token permissions and expiration

Performance Issues

Check cache TTL settings
Monitor API rate limits
Use more specific search filters
Consider increasing JIRA_REQUEST_TIMEOUT

🔒 Security

Never commit credentials to version control
Use environment variables for sensitive data
Rotate tokens regularly
Use least-privilege access tokens
Monitor API usage and access logs

📊 Monitoring & Debugging

Set log levels for debugging:

RUST_LOG=debug ./target/debug/jira-mcp-server     # Debug level
RUST_LOG=trace ./target/debug/jira-mcp-server     # Verbose trace level

Log output includes:

Tool invocations and parameters
JIRA API calls and responses
Cache operations and hit/miss rates
Performance timing information
Error details and stack traces

🤝 Contributing

Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request

📄 License

This project is licensed under the MIT License. See LICENSE for details.

🆘 Support & Resources

🎉 Happy JIRA automation with AI!

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

2dRelease cycle

10Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wunderfrucht/gouqi-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server