# alces-mcp [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://gitlab.com/moosejudge/alces-mcp  
**npm Downloads (last month):** 888  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/alces-mcp

## Description
Alces for Jira Data Center — MCP server bridging Jira DC/JSM with AI agents

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "alces-mcp": {
    "command": "npx",
    "args": ["-y","alces-mcp"]
  }
}
```

## Documentation

## What alces-mcp MCP server does

The alces-mcp MCP server is described as a bridge between AI agents and Jira Data Center, including Jira Service Management. Its purpose is to make Jira-related capabilities available through the Model Context Protocol. The provided description identifies the connected systems and the intended agent-facing use, but it does not specify which Jira resources or actions are exposed.

For a team evaluating integrations, the main fit is an environment that runs Jira Data Center or Jira Service Management and wants to connect those systems to an MCP-compatible AI agent. The listing does not establish whether the server supports reading issues, creating or editing records, searching, comments, projects, users, service requests, or any other Jira operation. Those details should be confirmed in the repository before implementation.

## Limitations and notes

The available material is limited to the project name, repository URL, category, and a short description. It does not include the README or technical documentation. As a result, this reference cannot verify installation commands, required runtime versions, transport mode, authentication method, permissions, environment variables, client setup, or supported Jira Data Center and JSM versions.

The alces-mcp MCP server should therefore be treated as an identified Jira DC/JSM integration rather than a fully documented deployment option. No specific MCP tools can be listed from the supplied material. The integration may expose Jira functions, but naming those functions or describing their inputs and outputs would go beyond the available evidence.

Before adopting alces-mcp MCP server, inspect the source repository for setup instructions and confirm how it reaches the Jira instance. Check whether the deployment requires network access to an internal Jira Data Center installation, what credentials or tokens it accepts, and how Jira permissions affect agent actions. Also verify whether Jira Service Management features are distinct from general Jira Data Center features in the implementation.

The repository is hosted at GitLab under the `moosejudge/alces-mcp` path. No license information is provided here. Client compatibility is also undocumented, so an MCP client should not be assumed to work without checking its connection requirements against the server's actual transport and configuration.

_Full upstream README: https://allmcps.com/mcp/alces-mcp/readme_