com.moosejudge/alces-mcp
Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
alces-mcpclaude mcp add alces-mcp -e 'JIRA_URL=<JIRA_URL>' -e 'JIRA_USER_TOKEN=<your jira_user_token>' -e 'JIRA_ADMIN_TOKEN=<your jira_admin_token>' -e 'JIRA_TIMEOUT_MS=30000' -e 'ALCES_TOOL_GROUPS=core-issues' -e 'ALCES_TOKEN_ESCALATION_DOMAINS=<ALCES_TOKEN_ESCALATION_DOMAINS>' -e 'JIRA_SESSION_USERNAME=<JIRA_SESSION_USERNAME>' -e 'JIRA_SESSION_PASSWORD=<your jira_session_password>' -- npx -y alces-mcp@1.1.0
{
"mcpServers": {
"alces-mcp": {
"command": "npx",
"args": [
"-y",
"alces-mcp@1.1.0"
],
"env": {
"JIRA_URL": "<JIRA_URL>",
"JIRA_USER_TOKEN": "<your jira_user_token>",
"JIRA_ADMIN_TOKEN": "<your jira_admin_token>",
"JIRA_TIMEOUT_MS": "30000",
"ALCES_TOOL_GROUPS": "core-issues",
"ALCES_TOKEN_ESCALATION_DOMAINS": "<ALCES_TOKEN_ESCALATION_DOMAINS>",
"JIRA_SESSION_USERNAME": "<JIRA_SESSION_USERNAME>",
"JIRA_SESSION_PASSWORD": "<your jira_session_password>"
}
}
}
}
Environment variables
JIRA_URLrequired Base URL of the Jira Data Center instanceJIRA_USER_TOKENrequired secret Personal Access Token for standard operationsJIRA_ADMIN_TOKENsecret Personal 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_PASSWORDsecret Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools.
Frequently asked questions
What is com.moosejudge/alces-mcp?
Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
How do I install com.moosejudge/alces-mcp?
It runs on your machine. In Claude Code: claude mcp add alces-mcp -e 'JIRA_URL=<JIRA_URL>' -e 'JIRA_USER_TOKEN=<your jira_user_token>' -e 'JIRA_ADMIN_TOKEN=<your jira_admin_token>' -e 'JIRA_TIMEOUT_MS=30000' -e 'ALCES_TOOL_GROUPS=core-issues' -e 'ALCES_TOKEN_ESCALATION_DOMAINS=<ALCES_TOKEN_ESCALATION_DOMAINS>' -e 'JIRA_SESSION_USERNAME=<JIRA_SESSION_USERNAME>' -e 'JIRA_SESSION_PASSWORD=<your jira_session_password>' -- npx -y alces-mcp@1.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does com.moosejudge/alces-mcp need an API key?
Yes. It expects JIRA_URL, JIRA_USER_TOKEN, JIRA_ADMIN_TOKEN, JIRA_SESSION_PASSWORD, which you set in its configuration.
Who maintains com.moosejudge/alces-mcp?
It is published by com.moosejudge. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.