Skip to main content
Glama
vertliba

jira-minimal-mcp

by vertliba
README.md
# jira-minimal-mcp

Minimal MCP server for Jira. Only ~150-1500 tokens vs ~25,000 for official Atlassian MCP.

## Installation

### Docker (recommended)

```bash
docker pull vertliba/jira-minimal-mcp
```

### uv (local)

```bash
uv tool install git+https://github.com/vertliba/jira-minimal-mcp
```

## Usage

### Basic (only get_issue, ~150 tokens)

```bash
docker run -i --rm \
  -e JIRA_URL=https://xxx.atlassian.net \
  -e JIRA_USERNAME=user@example.com \
  -e JIRA_API_TOKEN=xxx \
  vertliba/jira-minimal-mcp
```

### With additional features

```bash
docker run -i --rm \
  -e JIRA_URL=https://xxx.atlassian.net \
  -e JIRA_USERNAME=user@example.com \
  -e JIRA_API_TOKEN=xxx \
  vertliba/jira-minimal-mcp \
  --enable-search --enable-comments
```

### All features (~1500 tokens)

```bash
docker run -i --rm \
  -e JIRA_URL=https://xxx.atlassian.net \
  -e JIRA_USERNAME=user@example.com \
  -e JIRA_API_TOKEN=xxx \
  vertliba/jira-minimal-mcp \
  --enable-all
```

## CLI Arguments

| Argument | Description | Tools |
|----------|-------------|-------|
| (none) | Base functionality | `jira_get_issue` |
| `--enable-search` | JQL queries | `jira_search` |
| `--enable-create` | Create issues | `jira_create_issue` |
| `--enable-update` | Update issues | `jira_update_issue`, `jira_assign_issue` |
| `--enable-comments` | Comments | `jira_add_comment`, `jira_get_comments` |
| `--enable-all` | All tools | All of the above |

## Environment Variables

| Variable | Required | Description |
|----------|----------|-------------|
| `JIRA_URL` | Yes | Jira instance URL (e.g., `https://xxx.atlassian.net`) |
| `JIRA_USERNAME` | Yes | Jira username/email |
| `JIRA_API_TOKEN` | Yes | Jira API token ([create here](https://id.atlassian.com/manage-profile/security/api-tokens)) |

## MCP Client Configuration

### Claude Code (.mcp.json)

```json
{
  "mcpServers": {
    "jira": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "--network", "host",
        "-e", "JIRA_URL", "-e", "JIRA_USERNAME", "-e", "JIRA_API_TOKEN",
        "vertliba/jira-minimal-mcp", "--enable-search"],
      "env": {
        "JIRA_URL": "https://xxx.atlassian.net",
        "JIRA_USERNAME": "user@example.com",
        "JIRA_API_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}
```

### Codex (config.toml)

```toml
[mcp_servers.jira]
command = "docker"
args = ["run", "-i", "--rm", "--network", "host",
  "-e", "JIRA_URL", "-e", "JIRA_USERNAME", "-e", "JIRA_API_TOKEN",
  "vertliba/jira-minimal-mcp", "--enable-search"]
env = { JIRA_URL = "https://xxx.atlassian.net", JIRA_USERNAME = "user@example.com", JIRA_API_TOKEN = "YOUR_TOKEN" }
```

### Local (uv)

```json
{
  "mcpServers": {
    "jira": {
      "command": "uv",
      "args": ["run", "jira-minimal-mcp", "--enable-search"],
      "env": {
        "JIRA_URL": "https://xxx.atlassian.net",
        "JIRA_USERNAME": "user@example.com",
        "JIRA_API_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}
```

## Why?

The official Atlassian MCP server includes 28 tools and consumes ~25,000 tokens of context on every request. This is wasteful if you only need to read issues.

`jira-minimal-mcp` starts with just 1 tool (~150 tokens) and lets you add only what you need.

## License

MIT

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or ambiguity between tools.

Naming Consistency5/5

The single tool follows a consistent verb_noun pattern (jira_get_issue), so naming is perfectly consistent.

Tool Count2/5

A single tool for a Jira server is too few; typical usage requires multiple operations like create, update, or search, making this feel incomplete despite the 'minimal' label.

Completeness1/5

Only a read operation is provided; missing essential operations like create, update, delete, and search, leaving the surface severely incomplete for any meaningful workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues