Skip to content
mcp/skillhub

Alces MCP Server

com.moosejudge/alces-mcpv1.1.0

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

Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active17d ago

Install Alces MCP server

Install in Claude Code

claude mcp add alces -e JIRA_URL='<jira-url>' -e JIRA_USER_TOKEN='<jira-user-token>' -e JIRA_ADMIN_TOKEN='<jira-admin-token>' -e JIRA_SESSION_PASSWORD='<jira-session-password>' -- npx -y alces-mcp

Configuration

VariableRequiredSecretDescription
JIRA_URLyes—Base URL of the Jira Data Center instance
JIRA_USER_TOKENyesyesPersonal Access Token for standard operations
JIRA_ADMIN_TOKEN—yesPersonal 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—yesPassword for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools.

Freshness

Active — last maintenance signal 17d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    no data · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-09-22 · 17d ago · official registry · v1.1.0

FAQ

›How do I install the Alces MCP server in Claude Code?

Run: claude mcp add alces -e JIRA_URL='<jira-url>' -e JIRA_USER_TOKEN='<jira-user-token>' -e JIRA_ADMIN_TOKEN='<jira-admin-token>' -e JIRA_SESSION_PASSWORD='<jira-session-password>' -- npx -y alces-mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Alces require an API key?

Yes. It expects JIRA_URL, JIRA_USER_TOKEN, JIRA_ADMIN_TOKEN, JIRA_SESSION_PASSWORD, of which 3 are secrets.

›Can I use Alces as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Alces in the official MCP registry?

Yes, as com.moosejudge/alces-mcp.

Alternatives to Alces

Other project management MCP servers.

View all