Jira Easy MCP server

jira-easy-mcp

Another Model Context Protocol (MCP) server for Jira, without Auth token. Provides tools for complete Jira automation including issues, projects, boards, sprints, comments, worklogs, and more.

Tested on: Jira Server / Data Center 7.13, 8.20, 9.12 and 10.3 (every tool, automated, see Development & Testing)

🔑 Why This MCP?

Works with Basic Authentication (username + password) — no API tokens required!

Most Jira MCP servers require OAuth or API tokens, which many organizations restrict or don't allow. This MCP uses HTTP Basic Authentication, so you can connect using just your Jira username and password. Perfect for:

• 🏢 Enterprise environments where admins don't allow API token creation
• 🔒 Self-hosted Jira Server instances without OAuth configured
• ⚡ Quick setup without going through IT approval processes

Quick Start

VS Code (Workspace Configuration)

Create .vscode/mcp.json in your workspace root:

{
  "servers": {
    "jira": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "jira-easy-mcp"],
      "env": {
        "JIRA_BASE_URL": "https://your-jira-instance.com",
        "JIRA_USERNAME": "your-username",
        "JIRA_PASSWORD": "your-password",
        "JIRA_PROJECTS_FILTER": "ABC,DEF,XYZ",
        "JIRA_RESPONSE_FORMAT": "JSON"
      }
    }
  }
}

Add to your VS Code settings for accessing in all workspaces.

Note: JIRAPROJECTSFILTER and JIRARESPONSEFORMAT are optional. Projects filter limits access to specified projects. Response format can be JSON (default) or TOON (text-oriented notation).

Claude Code

claude mcp add jira \
  -e JIRA_BASE_URL=https://your-jira-instance.com \
  -e JIRA_USERNAME=your-username \
  -e JIRA_PASSWORD=your-password \
  -- npx -y jira-easy-mcp

Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.jira]
command = "npx"
args = ["-y", "jira-easy-mcp"]
env = { JIRA_BASE_URL = "https://your-jira-instance.com", JIRA_USERNAME = "your-username", JIRA_PASSWORD = "your-password" }

Other clients

Cursor: ~/.cursor/mcp.json or .cursor/mcp.json (use "mcpServers": { ... } wrapper) Windsurf: Add to your Windsurf MCP settings (use "mcpServers": { ... } wrapper) Claude Desktop: Edit claudedesktopconfig.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\; use "mcpServers": { ... } wrapper) Gemini CLI: ~/.gemini/settings.json (use "mcpServers": { ... } wrapper)

All use the same command, args, and env configuration as VS Code above.

Windows: if the client cannot start npx, use "command": "cmd" with "args": ["/c", "npx", "-y", "jira-easy-mcp"].

Tool limits: some clients (notably Cursor) cap how many tools they send to the model, historically around 40 across all servers. This server has 41; turn off the ones you don't need in the client's MCP settings.

Credentials from the OS keychain (optional)

To keep your password out of config files, omit JIRAUSERNAME/JIRAPASSWORD and store a credential under the service name JiraMCP:

• macOS: security add-generic-password -s JiraMCP -a your-username -w (prompts for the password; on first start macOS asks to allow node to read it)
• Windows: cmdkey /generic:JiraMCP /user:your-username /pass (use /generic, not /add)

If several accounts are stored, set JIRAUSERNAME to choose one. When both JIRAUSERNAME and JIRA_PASSWORD are set, they are used and the keychain is not read. Keychain support uses the optional keytar package; if it can't be installed on your machine, use the environment variables.

Common Use Cases

Shortened. The full README is on GitHub.