# rust-works/omni-dev [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/rust-works/omni-dev  
**GitHub Stars:** 1  
**npm Downloads (last month):** 1025543  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rust-works-omni-dev

## Description
MCP server for Atlassian Jira and Confluence with schema-validated Markdown↔ADF conversion. Catches content-model violations at conversion time rather than silently dropping ADF-only nodes like panels, mentions, and layouts.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "omni-dev": {
    "command": "npx",
    "args": ["-y","@modelcontextprotocol/inspector"]
  }
}
```

## Documentation

## What rust-works/omni-dev MCP server does

The rust-works/omni-dev MCP server is intended for working with Atlassian Jira and Confluence through the Model Context Protocol. Its stated focus is content handling: converting between Markdown and Atlassian Document Format (ADF) while checking the result against a schema.

That validation matters when content contains structures that ordinary Markdown conversion may not represent directly. The supplied description specifically identifies panels, mentions, and layouts as ADF-only nodes that can otherwise be dropped without an explicit error. The project is therefore relevant to agents that need to preserve Atlassian document structure rather than treating all content as plain Markdown.

## How it works

The rust-works/omni-dev MCP server uses schema validation during Markdown-to-ADF and ADF-to-Markdown conversion. Instead of accepting a conversion that loses unsupported content, it is described as catching content-model violations at conversion time. This gives the calling workflow an opportunity to detect a problem while content is being transformed.

The available material does not describe the individual MCP tool names, request parameters, response formats, or the exact Jira and Confluence operations exposed to clients. It supports the narrower conclusion that the server targets Atlassian content and emphasizes validation around the Markdown and ADF boundary.

## Tools and capabilities

Supported capabilities described in the source material include:

- Connecting MCP workflows with Atlassian Jira and Confluence.
- Converting Markdown to ADF.
- Converting ADF to Markdown.
- Validating converted content against a schema.
- Detecting content-model violations during conversion.
- Identifying loss risks for panels, mentions, and layouts.

The description does not confirm whether the server can create, update, search, or delete Jira issues or Confluence pages. Those operations should not be assumed without additional project documentation.

## Limitations and notes

The rust-works/omni-dev MCP server’s available description does not provide installation commands, configuration keys, authentication details, supported MCP clients, licensing information, or runtime requirements. It also does not specify how Jira and Confluence credentials are supplied. Those details must be verified in the repository before deployment.

The conversion behavior is described at the schema level, but the source does not define every supported ADF node or explain how validation failures are returned. Panels, mentions, and layouts are examples of structures the project is designed to protect from silent loss, not a complete list of supported content types.

Use this project when schema-aware Atlassian document conversion is the deciding requirement. For broader Jira or Confluence automation, confirm the repository’s actual tool surface and authentication model first. The rust-works/omni-dev MCP server should not be treated as a general Atlassian API wrapper based only on the supplied description.

_Full upstream README: https://allmcps.com/mcp/rust-works-omni-dev/readme_