mcp-server-atlassian (Rust port)

Rust implementation of the Atlassian MCP servers — connects AI assistants (Claude Desktop, Cursor, Continue, Cline, any MCP client) to Bitbucket Cloud and Jira Cloud through a single binary. Ports both @aashari/mcp-server-atlassian-bitbucket and @aashari/mcp-server-atlassian-jira with byte-for-byte parity on tool descriptions, schemas, output formats, and error envelopes.

This directory does not ship to npm. It builds a single static-ish binary: mcp-atlassian.

Why a Rust port

• No Node.js runtime dependency.
• ~13 MB release binary vs. ~120 MB node_modules tree.
• Cold-start in milliseconds instead of hundreds.
• One binary serves both Bitbucket and Jira — instead of running two Node processes side-by-side, you get one MCP server exposing all 11 tools (six bb_*, five jira_*).
• Identical LLM-facing tool descriptions and output formats — drop-in replacement for the TS packages in an MCP client config.

Download prebuilt binaries

Grab the latest release for your platform from the GitHub Releases page:

Each archive ships the mcp-atlassian binary and a .sha256 checksum sibling. On macOS you may need to clear the quarantine bit: xattr -d com.apple.quarantine ./mcp-atlassian.

Build from source

git clone https://github.com/huskercane/mcp-server-atlassian-rs.git
cd mcp-server-atlassian-rs
cargo build --release

The binary lands at target/release/mcp-atlassian. Requires Rust 1.85 or later.

Optional checks:

cargo test                                   # full test suite
cargo clippy --all-targets -- -D warnings   # lint gate (pedantic)
cargo deny check                             # license + advisory check

Credentials

Create an Atlassian API token with the scopes you need (Bitbucket and/or Jira). The TS README has step-by-step screenshots: see Get Your Bitbucket Credentials.

Environment variables

Tokens can also be written to ~/.mcp/configs.json. The Rust port supports per-vendor sections (bitbucket, atlassian-bitbucket, jira, atlassian-jira) so Bitbucket-only and Jira-only keys stay isolated:

{
  "bitbucket": {
    "environments": {
      "ATLASSIAN_USER_EMAIL": "you@company.com",
      "ATLASSIAN_API_TOKEN": "ATATT...",
      "BITBUCKET_DEFAULT_WORKSPACE": "acme"
    }
  },
  "jira": {
    "environments": {
      "ATLASSIAN_SITE_NAME": "mycompany"
    }
  }
}

Shared keys (e.g. ATLASSIAN_API_TOKEN) can live in either section — when the same key a

... View full README on GitHub