atlassian-marketplace-mcp

A Model Context Protocol server that exposes the Atlassian Marketplace vendor APIs (reporting + v1 promotions) as 95 tools, 3 resources, and 4 prompts. Lets an LLM look up licenses, query transactions, manage promotions, read reviews, pull churn/conversion/renewal metrics, inspect app listings, and more — without you writing curl one-liners. Every tool is annotated per the MCP 2024-11 spec (readOnlyHint / destructiveHint) so MCP-aware UIs can render safety warnings automatically.

Targets Marketplace vendors (people who sell apps on marketplace.atlassian.com). Not for end users of Marketplace apps.

What is MCP? Model Context Protocol is an open standard for connecting AI assistants (Claude, etc.) to external data sources and tools. This server runs as a child process of your MCP client (Claude Code, Claude Desktop, etc.) and speaks MCP over stdio.

What's covered

Full per-tool catalog: docs/TOOLS.md. Design notes: docs/ARCHITECTURE.md.

Related MCP server: Atlassian MCP Server

Prerequisites

• Node.js ≥ 20 (uses native fetch and ES modules)

• An Atlassian account with vendor access to your developer space

• An Atlassian API token — create one at id.atlassian.com → Security → API tokens

Install

git clone <this repo>
cd Atlassian_mcp
npm install
npm run build

Configure

Copy the example env file and fill it in:

cp .env.example .env        # macOS / Linux / PowerShell
# Windows cmd.exe:  copy .env.example .env

The four required variables:

Finding your developerId and partnerId

Both are visible in the Atlassian Marketplace partner console URL when you're logged in, or you can resolve developerId from vendorId via the API:

# Replace EMAIL, TOKEN, VENDOR_ID with yours
curl -u "EMAIL:TOKEN" \
  "https://api.atlassian.com/marketplace/rest/3/developer-space/vendor/VENDOR_ID"

The numeric partnerId shows up in the Marketplace partner console URL (e.g. marketplace.atlassian.com/manage/vendors/<partnerId>). Often it's the same number as your vendorId, but not always — verify.

Optional: known product IDs

Add PRODUCT_ID_<UPPER_SNAKE>=<uuid> lines to .env for each of your apps. They're then accessible via the apps_known tool as a friendly-name → UUID map, so the LLM can say "My App Name" without having to call apps_list every time.

Discover the right UUIDs first via:

node dist/server.js  # in another shell, send tools/call apps_list
# Or use the apps_list MCP tool from a connected client.

npm scripts

Run

npm start
# or directly:
node dist/server.js

The server speaks MCP over stdio. It will wait for an MCP client to connect. To smoke-test by hand:

# Send a tools/list request via stdin to see all 95 tools (macOS / Linux)
printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"sh","version":"0"}}}' \
  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' | node dist/server.js

On Windows (PowerShell) the same smoke test is:

@'
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"ps","version":"0"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":2,"method":"tools/list"}
'@ | node dist/server.js

Wire into Claude Code

Add this to your ~/.claude.json under mcpServers (or a project-local .mcp.json). On Windows the file lives at %USERPROFILE%\.claude.json; use a Windows-style absolute path in args (forward slashes are fine in JSON):

{
  "mcpServers": {
    "atlassian-marketplace": {
      "command": "node",
      "args": ["/absolute/path/to/Atlassian_mcp/dist/server.js"]
    }
  }
}

// Windows example args:
"args": ["C:/Users/you/Atlassian_mcp/dist/server.js"]

The server finds its .env in the repo root even when the MCP client launches it from a different working directory, so no env block is needed in the client config (though you can use one to override).

Restart Claude Code. The 95 tools are then available as mcp__atlassian-marketplace__* in your next session.

Example prompts

Once wired in, try:

• "Show me the last 10 transactions in Q1 2026 for <my app>."

• "What's our cloud churn rate this month?"

• "List all active promotions expiring this quarter."

• "Look up license SEN-LXXXXXXXX and tell me when it expires."

• "Pull customer insights by region for <my app>."

• "Create a 25% promo code for <my app>, valid until 2026-12-31, single-use, Cloud annual."

Troubleshooting

Project structure

src/
├─ server.ts                # MCP stdio entrypoint, registers all 25 tool modules
├─ config.ts                # env loader, single API base, PRODUCT_ID_* map
├─ http-client.ts           # Basic-auth fetch wrapper, 429 retry
└─ tools/
   ├─ _shared.ts            # jsonResult, asQuery, REPORTING_BASE/PROMO_BASE, filter schemas
   ├─ apps.ts               # apps_list, apps_known
   ├─ promotions.ts         # 10 promo tools (v1)
   ├─ licenses.ts           # 5 license tools (reporting)
   ├─ transactions.ts       # 7 transaction tools (reporting)
   ├─ reporting-meta.ts     # reporting_links
   ├─ evaluations.ts        # evaluations_by_metric
   ├─ feedback.ts           # 2 feedback tools
   ├─ customer-insights.ts  # 4 customer insights tools
   ├─ sales-metrics.ts      # 6 sales-metric tools
   ├─ benchmarks.ts         # 2 benchmark tools
   ├─ marketing-attribution.ts # 3 async-export tools
   ├─ app-requests.ts       # app_requests_and_approvals
   ├─ reviews.ts            # 4 review tools
   ├─ search-keywords.ts    # 8 keyword tools
   ├─ free-starter.ts       # free_starter_tier_export
   ├─ app-listing.ts        # 2 product listing tools
   ├─ app-software.ts       # 7 app-software tools
   ├─ app-version-listing.ts# 4 version-listing tools
   ├─ privacy-security.ts   # 4 privacy/security tools
   ├─ migrations.ts         # 3 cloud-migration compat tools
   ├─ parent-software.ts    # 5 parent-software tools
   ├─ developer-space.ts    # 9 dev-space admin tools
   ├─ partner-metrics.ts    # partner_metrics_fetch
   ├─ product-catalog.ts    # product_catalog_latest
   └─ artifacts.ts          # artifact_fetch_from_url, artifact_get

Further reading

• docs/TOOLS.md — every tool with its args

• docs/ARCHITECTURE.md — design decisions and gotchas

• docs/CHANGELOG.md — version history

• Atlassian Marketplace API reference: https://developer.atlassian.com/platform/marketplace/rest/v4/ (Atlassian's docs site versions the content as /v4/. The URL paths we actually hit are still /rest/3/... — that's the wire format. The older /v3/ docs path on the developer site corresponds to the deprecated v2 wire format and is NOT what this MCP targets.)

• Model Context Protocol spec: https://modelcontextprotocol.io/

License

MIT © 2026 Rustem Shiriiazdanov. Use it, fork it, ship it.