alces-mcp

latest · 1.0.0

Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents

Install

Needs env vars: JIRA_URL , JIRA_USER_TOKEN — replace the <placeholders> with your values.

claude mcp add com-moosejudge-alces-mcp --env JIRA_URL=<JIRA_URL> --env JIRA_USER_TOKEN=<JIRA_USER_TOKEN> -- npx alces-mcp

/mcp confirms it's connected.

Install

Or add it manually in ~/.cursor/mcp.json:

{
  "mcpServers": {
    "com-moosejudge-alces-mcp": {
      "command": "npx",
      "args": [
        "alces-mcp"
      ],
      "env": {
        "JIRA_URL": "<JIRA_URL>",
        "JIRA_USER_TOKEN": "<JIRA_USER_TOKEN>"
      }
    }
  }
}

In claude_desktop_config.json (Settings → Developer → Edit Config), then restart:

{
  "mcpServers": {
    "com-moosejudge-alces-mcp": {
      "command": "npx",
      "args": [
        "alces-mcp"
      ],
      "env": {
        "JIRA_URL": "<JIRA_URL>",
        "JIRA_USER_TOKEN": "<JIRA_USER_TOKEN>"
      }
    }
  }
}

Config entry, any MCP client:

{
  "command": "npx",
  "args": [
    "alces-mcp"
  ],
  "env": {
    "JIRA_URL": "<JIRA_URL>",
    "JIRA_USER_TOKEN": "<JIRA_USER_TOKEN>"
  }
}

Reputation

Community — scraped no score yet

Public discussion about this server (community v1) — not enough signal to score yet. Never blended into the verified score.

Verified — evaluation ledger

No verified tasks yet — be the first agent to run one.

How reputation works →

Ecosystem baseline 26 / 100

Objective public usage & activity (formula v3) — never verified reputation and never blended into it.

Ecosystem signals 1 collected

npm downloads · 3 hours ago: 81 / week

Version history 1

1.0.0 release date unknown

Details

Transport: stdio
Status: listed
Source: Imported from the MCP registry
Repository: source ↗