Loading
Alces
Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
接入你的智能体
添加此服务器
The publisher's own command. Not a PlugMCP endpoint.
Local command
npx -y [email protected]
Credentials from the publisher
- JIRA_URL — Base URL of the Jira Data Center instance
- JIRA_USER_TOKEN — 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.
Provider
Claude Code
JIRA_URL=<value> JIRA_USER_TOKEN=<secret> JIRA_ADMIN_TOKEN=<secret> JIRA_TIMEOUT_MS=<value> ALCES_TOOL_GROUPS=<value> ALCES_TOKEN_ESCALATION_DOMAINS=<value> JIRA_SESSION_USERNAME=<value> JIRA_SESSION_PASSWORD=<secret> claude mcp add com.moosejudge-alces-mcp -- npx -y [email protected]
Run in a terminal.
Claude Desktop
{
"mcpServers": {
"com.moosejudge-alces-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"JIRA_URL": "<value>",
"JIRA_USER_TOKEN": "<secret>",
"JIRA_ADMIN_TOKEN": "<secret>",
"JIRA_TIMEOUT_MS": "<value>",
"ALCES_TOOL_GROUPS": "<value>",
"ALCES_TOKEN_ESCALATION_DOMAINS": "<value>",
"JIRA_SESSION_USERNAME": "<value>",
"JIRA_SESSION_PASSWORD": "<secret>"
}
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Related MCP
View more- Firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
- NNotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
- Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
Related skills
View all- reaReverse engineer anything with agents, from app behavior down to native binaries.
- rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
- rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
README is not crawled yet. Open the repository
- How do I install Alces?
- Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
- Does Alces need an API key?
- The publisher lists these environment variables: JIRA_URL, JIRA_USER_TOKEN, JIRA_ADMIN_TOKEN, JIRA_TIMEOUT_MS, ALCES_TOOL_GROUPS, ALCES_TOKEN_ESCALATION_DOMAINS, JIRA_SESSION_USERNAME, JIRA_SESSION_PASSWORD.
- What transport does Alces use?
- Alces runs locally over stdio.
- When was Alces last checked?
- Last checked 2026-10-16. Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents
No tool list yet. Remote servers get one after the first health check.