Alces MCP server

by moosejudge.com·com.moosejudge/alces-mcp·v1.1.0

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

C55/100grade C

What users say

No reviews yet

Safety scan

C55/100

Adoption

New

104 downloads/wk

Reviews

Nobody has reviewed Alces yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it

no findings

Code scan93 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancerepository not readable: unknown3/15
Maintainer identityno repository or website to verify2/10

Overall 55/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 55/100; higher than 10% of 1,119 Developer tools servers
Downloads a week: 104; more than 60% of 436 Developer tools servers with a package

Release history: 2 versions in the registry since 2026-09-16, latest 2026-09-22, typically one every 7 days.

Runs npx -y alces-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add alces-mcp -- npx -y alces-mcp

Is Alces MCP server safe?: With care: it is graded C, so read the findings first (55/100). Read the Alces safety report
How do I install Alces?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Alces need an API key?: Yes. The registry entry asks for JIRA_USER_TOKEN, JIRA_ADMIN_TOKEN, JIRA_SESSION_PASSWORD.
Is Alces maintained?: The latest release is v1.1.0.
What can I use instead of Alces?: Servers from other publishers that do the same job: Atlassian Dc Jira MCP server, Jira Alerts (JSM Operations) MCP server and Atlassian Rovo MCP Server.
How does Alces compare with other Developer tools MCP servers?: safety score 55/100 (higher than 10% of 1,119 Developer tools servers); downloads a week 104 (more than 60% of 436 Developer tools servers with a package). Full comparison.

Same job from other publishers: the closest match first, then the best rated.

Atlassian Dc Jira
MCP server for Atlassian Jira Data Center - search, view, and create issues
not reviewed
Established
B
Jira Alerts (JSM Operations)
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
not reviewed
Growing
B
Atlassian Rovo MCP Server
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
not reviewed
Established
A
Jira Stdio
MCP server for Jira Cloud — issues, search, comments, attachments, transitions.
not reviewed
Growing
B
Atlassian Extended
Jira/Confluence MCP server (MCP 2026-07-28): sprints, boards, attachments; writes or read-only
not reviewed
Growing
B

Local package. It runs on your machine, not through the gateway.

JIRA_URLBase URL of the Jira Data Center instance
JIRA_USER_TOKENsecretPersonal Access Token for standard operations
JIRA_ADMIN_TOKENsecretPersonal Access Token for elevated/admin operations (optional)
JIRA_TIMEOUT_MSTimeout in milliseconds for every Jira API call. Defaults to 30000 (30s) when unset or blank; raise it if your instance is slow.
ALCES_TOOL_GROUPSComma-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_DOMAINSComma-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_USERNAMEOptional 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_PASSWORDsecretPassword for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools.

Claim it to keep the listing current and reply to reviews. Claiming never changes the grade or hides a review.

Shows the safety grade and links back to this page. It updates itself after every scan and review.

[![mcp.market](https://mcp.market/badge/moosejudge-alces-mcp.svg)](https://mcp.market/server/moosejudge-alces-mcp)