Alces Mcp

Lets an assistant read and manage Jira Data Center and Jira Service Management issues, projects, assets, and users through a local MCP server.

What you can do

Alces bridges Jira Data Center and Jira Service Management to AI agents over stdio. Its tools are grouped into domains such as core issues, service desk, assets, issue detail, agile, projects, filters and personal settings, and users and groups, with a core-issues set active by default. It supports standard operations with a personal access token and optional elevated admin operations, plus legacy avatar upload, crop, and finalize tools that use session-cookie authentication.

When to use it

Worth adding when an assistant needs to work with a self-hosted Jira Data Center or JSM instance: looking up and updating issues, browsing projects and agile boards, handling service desk requests, or querying assets. It is not for Jira Cloud, since it targets the Data Center base URL.

Requirements

Runs locally as an npm package (alces-mcp) over stdio, so Node.js is needed. Requires JIRA_URL, the base URL of the Jira Data Center instance, and JIRA_USER_TOKEN, a personal access token for standard operations. Optional: JIRA_ADMIN_TOKEN for elevated operations, JIRA_SESSION_USERNAME and JIRA_SESSION_PASSWORD for session-cookie auth on the legacy avatar tools, JIRA_TIMEOUT_MS, ALCES_TOOL_GROUPS, and ALCES_TOKEN_ESCALATION_DOMAINS.