com.moosejudge/alces-mcp

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

What does this entry provide?

com.moosejudge/alces-mcp is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 90/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding com.moosejudge/alces-mcp to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: Official MCP Registry
Quality: 90/100
Install method: npm
Repo: Registry only
Repo updated: Sep 22, 2026

Install command

npx -y alces-mcp@1.1.0

Install method: npm

Review the upstream source before running this command.

Source entry

Quality

Repo stars

Repo updated

Sep 22, 2026

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

MCP manifest

{
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "isLatest": true,
      "updatedAt": "2026-09-22T19:57:36.406826Z",
      "publishedAt": "2026-09-22T19:57:36.406826Z",
      "statusChangedAt": "2026-09-22T19:57:36.406826Z"
    }
  },
  "server": {
    "name": "com.moosejudge/alces-mcp",
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "version": "1.1.0",
    "packages": [
      {
        "version": "1.1.0",
        "transport": {
          "type": "stdio"
        },
        "identifier": "alces-mcp",
        "registryType": "npm",
        "environmentVariables": [
          {
            "name": "JIRA_URL",
            "format": "string",
            "isRequired": true,
            "description": "Base URL of the Jira Data Center instance"
          },
          {
            "name": "JIRA_USER_TOKEN",
            "format": "string",
            "isSecret": true,
            "isRequired": true,
            "description": "Personal Access Token for standard operations"
          },
          {
            "name": "JIRA_ADMIN_TOKEN",
            "format": "string",
            "isSecret": true,
            "description": "Personal Access Token for elevated/admin operations (optional)"
          },
          {
            "name": "JIRA_TIMEOUT_MS",
            "format": "string",
            "default": "30000",
            "description": "Timeout in milliseconds for every Jira API call. Defaults to 30000 (30s) when unset or blank; raise it if your instance is slow."
          },
          {
            "name": "ALCES_TOOL_GROUPS",
            "format": "string",
            "default": "core-issues",
            "description": "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."
          },
          {
            "name": "ALCES_TOKEN_ESCALATION_DOMAINS",
            "format": "string",
            "description": "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."
          },
          {
            "name": "JIRA_SESSION_USERNAME",
            "format": "string",
            "description": "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."
          },
          {
            "name": "JIRA_SESSION_PASSWORD",
            "format": "string",
            "isSecret": true,
            "description": "Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools."
          }
        ]
      }
    ],
    "repository": {
      "url": "https://gitlab.com/moosejudge/alces-mcp",
      "source": "gitlab"
    },
    "description": "Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents"
  }
}

Report an issue with this listing