PluginBench
MCP Server

com.moosejudge/alces-mcp MCP Server

com.moosejudge/alces-mcp

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the com.moosejudge/alces-mcp MCP server?

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

How to install com.moosejudge/alces-mcp

Copy-paste configuration for popular MCP clients.

transport: stdio
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • JIRA_URL
    required

    Base URL of the Jira Data Center instance

  • JIRA_USER_TOKEN
    required
    secret

    Personal Access Token for standard operations

  • JIRA_ADMIN_TOKEN
    secret

    Personal Access Token for elevated/admin operations (optional)

  • JIRA_TIMEOUT_MS

    Timeout in milliseconds for every Jira API call. Defaults to 30000 (30s) when unset or blank; raise it if your instance is slow.

  • ALCES_TOOL_GROUPS

    Comma-separated tool domains to pre-activate at startup instead of the core-issues default (core-issues, jsm-service-desk, assets, issue-detail, agile, projects, filters-personal-settings, users-groups-permissions, admin). Unknown names are warned about on stderr and ignored.

  • ALCES_TOKEN_ESCALATION_DOMAINS

    Comma-separated tool domains allowed to substitute JIRA_ADMIN_TOKEN via token escalation. Empty by default — no tool may escalate until its domain is listed here.

  • JIRA_SESSION_USERNAME

    Optional Jira DC account username (not a PAT), paired with JIRA_SESSION_PASSWORD, enabling session-cookie auth for the legacy avatar upload/crop/finalize tools. Must be the same account as JIRA_USER_TOKEN and must not be an administrator: those tools authenticate as this account rather than the token.

  • JIRA_SESSION_PASSWORD
    secret

    Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools.

~/Library/Application Support/Claude/claude_desktop_config.json
JSON config
{
  "mcpServers": {
    "alces-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "alces-mcp"
      ],
      "env": {
        "JIRA_URL": "<YOUR_JIRA_URL>",
        "JIRA_USER_TOKEN": "<YOUR_JIRA_USER_TOKEN>",
        "JIRA_ADMIN_TOKEN": "<YOUR_JIRA_ADMIN_TOKEN>",
        "JIRA_TIMEOUT_MS": "<YOUR_JIRA_TIMEOUT_MS>",
        "ALCES_TOOL_GROUPS": "<YOUR_ALCES_TOOL_GROUPS>",
        "ALCES_TOKEN_ESCALATION_DOMAINS": "<YOUR_ALCES_TOKEN_ESCALATION_DOMAINS>",
        "JIRA_SESSION_USERNAME": "<YOUR_JIRA_SESSION_USERNAME>",
        "JIRA_SESSION_PASSWORD": "<YOUR_JIRA_SESSION_PASSWORD>"
      }
    }
  }
}

Related MCP servers

Castor for Confluence Data Center — MCP server bridging Confluence DC with AI agents

View repository →

AI mixing and mastering: analyze your mixes, run DSP autofix, render stems, and master tracks.

AI-powered incident management and server monitoring via MCP.

Agent-readiness scanner (0-5 score), robots.txt + llms.txt generators, managed agent enablement.

0
View repository →

Manage customers, reviews, requests, and reputation for one More Good Reviews project.

Command your AI agents by voice: PTT rooms, channels, direct messages, agent email, memory (mRAG).

1
TypeScript
MIT
View repository →