Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
Alces-mcp is an MCP integration. Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents.
The published npm package is alces-mcp, version 1.1.0. Its declared MCP transport is stdio.
The package declares JIRA_URL (required): Base URL of the Jira Data Center instance; JIRA_USER_TOKEN (required): Personal Access Token for standard operations; JIRA_ADMIN_TOKEN: Personal 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: Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 1.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related productivity & project management MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| JIRA_URL | Base URL of the Jira Data Center instance | Yes |
| JIRA_USER_TOKEN | Personal Access Token for standard operations | Yes |
| JIRA_ADMIN_TOKEN | Personal Access Token for elevated/admin operations (optional) | 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. | Optional |
| 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. | Optional |
| 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. | Optional |
| 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. | Optional |
| JIRA_SESSION_PASSWORD | Password for JIRA_SESSION_USERNAME. Only used to establish a session cookie for the legacy avatar upload/crop/finalize tools. | Optional |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.