Alces MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add alces-mcp -e 'JIRA_URL=<JIRA_URL>' -e 'JIRA_USER_TOKEN=<JIRA_USER_TOKEN>' -- npx -y alces-mcp

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

[mcp_servers.alces-mcp]
command = "npx"
args = ["-y", "alces-mcp"]
env = { JIRA_URL = "<JIRA_URL>", JIRA_USER_TOKEN = "<JIRA_USER_TOKEN>" }

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

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

Put your own values in place of <JIRA_URL> (Base URL of the Jira Data Center instance), <JIRA_USER_TOKEN> (Personal Access Token for standard operations). The author’s registry entry marks them as required.

Optional settings from the registry entry, left out of the block above: JIRA_ADMIN_TOKEN (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 (Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools).