Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
Connect Runs on your machine
claude mcp add alces-mcp -e JIRA_URL=<JIRA_URL> -e JIRA_USER_TOKEN=<JIRA_USER_TOKEN> -e JIRA_ADMIN_TOKEN=<JIRA_ADMIN_TOKEN> -e JIRA_TIMEOUT_MS=<JIRA_TIMEOUT_MS> -e ALCES_TOOL_GROUPS=<ALCES_TOOL_GROUPS> -e ALCES_TOKEN_ESCALATION_DOMAINS=<ALCES_TOKEN_ESCALATION_DOMAINS> -e JIRA_SESSION_USERNAME=<JIRA_SESSION_USERNAME> -e JIRA_SESSION_PASSWORD=<JIRA_SESSION_PASSWORD> -- npx -y [email protected]{
"mcpServers": {
"alces-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"JIRA_URL": "<JIRA_URL>",
"JIRA_USER_TOKEN": "<JIRA_USER_TOKEN>",
"JIRA_ADMIN_TOKEN": "<JIRA_ADMIN_TOKEN>",
"JIRA_TIMEOUT_MS": "<JIRA_TIMEOUT_MS>",
"ALCES_TOOL_GROUPS": "<ALCES_TOOL_GROUPS>",
"ALCES_TOKEN_ESCALATION_DOMAINS": "<ALCES_TOKEN_ESCALATION_DOMAINS>",
"JIRA_SESSION_USERNAME": "<JIRA_SESSION_USERNAME>",
"JIRA_SESSION_PASSWORD": "<JIRA_SESSION_PASSWORD>"
}
}
}
}{
"mcpServers": {
"alces-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"JIRA_URL": "<JIRA_URL>",
"JIRA_USER_TOKEN": "<JIRA_USER_TOKEN>",
"JIRA_ADMIN_TOKEN": "<JIRA_ADMIN_TOKEN>",
"JIRA_TIMEOUT_MS": "<JIRA_TIMEOUT_MS>",
"ALCES_TOOL_GROUPS": "<ALCES_TOOL_GROUPS>",
"ALCES_TOKEN_ESCALATION_DOMAINS": "<ALCES_TOKEN_ESCALATION_DOMAINS>",
"JIRA_SESSION_USERNAME": "<JIRA_SESSION_USERNAME>",
"JIRA_SESSION_PASSWORD": "<JIRA_SESSION_PASSWORD>"
}
}
}
}{
"servers": {
"alces-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"JIRA_URL": "<JIRA_URL>",
"JIRA_USER_TOKEN": "<JIRA_USER_TOKEN>",
"JIRA_ADMIN_TOKEN": "<JIRA_ADMIN_TOKEN>",
"JIRA_TIMEOUT_MS": "<JIRA_TIMEOUT_MS>",
"ALCES_TOOL_GROUPS": "<ALCES_TOOL_GROUPS>",
"ALCES_TOKEN_ESCALATION_DOMAINS": "<ALCES_TOKEN_ESCALATION_DOMAINS>",
"JIRA_SESSION_USERNAME": "<JIRA_SESSION_USERNAME>",
"JIRA_SESSION_PASSWORD": "<JIRA_SESSION_PASSWORD>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
JIRA_URLRequired | Base URL of the Jira Data Center instance |
JIRA_USER_TOKENRequired, secret | Personal Access Token for standard operations |
JIRA_ADMIN_TOKENOptional, secret | Personal Access Token for elevated/admin operations (optional) |
JIRA_TIMEOUT_MSOptional | 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_GROUPSOptional | 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_DOMAINSOptional | 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_USERNAMEOptional | 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 tok… |
JIRA_SESSION_PASSWORDOptional, secret | Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools. |
Details
| Package | [email protected] (NPM, stdio) |
| First published | 22 Sep 2026 |
| Last updated | 22 Sep 2026 |
| Registry name | com.moosejudge/alces-mcp |
More productivity servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.