# Omni Dev > AI-powered git commit rewriter, PR generator, and MCP server for Jira, Confluence, and Datadog. Single Rust binary. - **Type:** MCP server - **Install:** `agentstack add mcp-rust-works-omni-dev` - **Verified:** Pending review - **Seller:** [rust-works](https://agentstack.voostack.com/s/rust-works) - **Installs:** 0 - **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml) - **Latest version:** 0.1.0 - **License:** BSD-3-Clause - **Upstream author:** [rust-works](https://github.com/rust-works) - **Source:** https://github.com/rust-works/omni-dev ## Install ```sh agentstack add mcp-rust-works-omni-dev ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # omni-dev [](https://crates.io/crates/omni-dev) [](https://docs.rs/omni-dev) [](https://github.com/rust-works/omni-dev/actions) [](LICENSE) An intelligent Git commit message toolkit with AI-powered contextual intelligence. Transform messy commit histories into professional, conventional commit formats with project-aware suggestions. ## 🎬 See It In Action [](https://asciinema.org/a/eJJf5Aj8N26JoCaUsAFVH8dqz) *Watch omni-dev transform messy commits into professional ones with AI-powered analysis* ## 30-Second Demo Transform your commit messages and create professional PRs with AI intelligence: ```bash # Analyze and improve commit messages in your current branch omni-dev git commit message twiddle 'origin/main..HEAD' --use-context # Before: "fix stuff", "wip", "update files" # After: "feat(auth): implement OAuth2 authentication system" # "docs(api): add comprehensive endpoint documentation" # "fix(ui): resolve mobile responsive layout issues" # Create a professional PR with AI-generated description omni-dev git branch create pr # πŸŽ‰ Generates comprehensive PR with detailed description, testing info, and more ``` ## ✨ Key Features - πŸ€– **AI-Powered Intelligence**: Claude AI analyzes your code changes to suggest meaningful commit messages and PR descriptions - 🧠 **Contextual Awareness**: Understands your project structure, conventions, and work patterns - πŸ” **Comprehensive Analysis**: Deep analysis of commits, branches, and file changes - ✏️ **Smart Amendments**: Safely improve single or multiple commit messages - πŸš€ **PR Creation**: Generate professional pull requests with AI-powered descriptions - πŸ“¦ **Automatic Batching**: Handles large commit ranges intelligently - 🎯 **Conventional Commits**: Automatic detection and formatting - 🌐 **Browser Bridge**: Drive HTTP requests through an authenticated browser tab without exfiltrating cookies or tokens - πŸ—‚οΈ **Worktrees View**: One live view of every repo and git worktree open across all your VS Code windows - πŸ›‘οΈ **Safety First**: Working directory validation, protection against amending commits already in remote main branches, and error recovery - ⚑ **Fast & Reliable**: Built with Rust for memory safety and performance ## πŸš€ Quick Start ### Installation ```bash # Install from crates.io cargo install omni-dev # Install with Nix nix profile install github:rust-works/omni-dev # Install with Nix flakes (development) nix run github:rust-works/omni-dev ``` **Next step:** see [Getting Started](docs/getting-started.md) β€” a 10-minute walkthrough from authentication to your first AI-improved commit. (For just the API-key reference, see [Authentication](docs/configuration.md#authentication).) #### Shell Completion `omni-dev completions ` prints a completion script to stdout for `bash`, `zsh`, `fish`, `powershell`, or `elvish`. The quickest path is bash per-user: ```bash # Add to ~/.bashrc: eval "$(omni-dev completions bash)" ``` See [docs/shell-completion.md](docs/shell-completion.md) for per-shell install recipes, the `$fpath`/`compinit` setup zsh requires, and troubleshooting. ## πŸ†š How omni-dev Compares omni-dev sits in two adjacent spaces β€” AI commit-message tooling and Atlassian/dev-workflow MCP servers. The tables below contrast the incumbents on the dimensions a first-time reader is most likely to weigh. In every cell, `βœ…` means full / native support, `⚠` means partial or available only with caveats, and `❌` means not supported β€” and omni-dev's own limitations are flagged just as honestly (the `⚠` marks in its own columns). Beyond these two niches, omni-dev also ships a supervised **daemon** that hosts a **browser bridge** (an authenticated proxy that runs requests through a logged-in browser tab for SSO-gated dashboards such as Grafana and Loki), a **Snowflake** SQL service (one external-browser SSO session reused for concurrent queries), and a **worktrees** registry (one live view of the repos open across every VS Code window), plus a local append-only **request log** (`omni-dev log`). These have no direct incumbent in either table below, so they are called out here rather than scored against tools that don't aim for them. ### vs AI commit tools | | omni-dev | [opencommit](https://github.com/di-sukharev/opencommit) | [aicommits](https://github.com/Nutlope/aicommits) | |-------------------------------------------------------|-------------------------------------|---------------------------------------------------------|---------------------------------------------------| | Rewrite existing commits in a range | βœ… `twiddle` | ❌ pre-commit only | ❌ pre-commit only | | Parallel batched processing (long ranges) | βœ… `--concurrency N` | ❌ | ❌ | | AI-written PR descriptions | βœ… `git branch create pr` | ⚠ GitHub Action only | ❌ | | Project-context awareness | βœ… `--use-context` | ❌ | ❌ | | Sandboxed `claude-cli` backend | βœ… [ADR-0028](docs/adrs/adr-0028.md) | ❌ | ❌ | | Multi-backend (Anthropic / Bedrock / OpenAI / Ollama) | βœ… | βœ… | βœ… | | Conventional Commits | βœ… | βœ… | ⚠ config | | Language / runtime | Rust (static binary) | Node.js | Node.js | ### vs Atlassian-workflow MCP servers omni-dev's MCP server also exposes Git tools (commit analysis, twiddling, PR creation), Datadog tools, and an `ai_chat` proxy β€” surfaces the Atlassian-focused servers don't aim for. The table below compares only Atlassian capability depth. | | omni-dev MCP | [sooperset/mcp-atlassian](https://github.com/sooperset/mcp-atlassian) | [Atlassian official (Rovo)](https://github.com/atlassian/atlassian-mcp-server) | |-----------------------------------------|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| | Jira REST surface | βœ… 36 tools (agile, fields, dev panel, links, watchers, worklogs, versions, changelog) | βœ… 49 tools (above + JSM, proforma forms, SLA, batch ops) | ⚠ 14 tools (basic CRUD, search, transitions, worklogs only) | | Confluence REST surface | βœ… 25 tools (history, diff, attachments, labels, spaces, inline + footer comments) | βœ… 24 tools (history, diff, attachments, labels; **no inline comments / spaces**) | ⚠ 12 tools (inline + footer comments, spaces; **no delete / move / history / diff / attachments / labels**) | | Lossless JFM ↔ ADF round-trip | βœ… full ADF node set (schema v56.0.9) + unsupported-node escape | ❌ | ⚠ raw ADF, model-dependent | | Anchored review-comment preservation | βœ… annotation marks survive round-trip | ❌ anchor stripped, comments orphaned | ⚠ ADF carries anchors; model-dependent | | Pre-flight ADF schema validation | βœ… nesting + arity, before write | ❌ | ❌ | | Offline JFM ↔ ADF conversion (no creds) | βœ… `atlassian_convert` | ❌ | ❌ | | Cloud + Server + Data Center | ⚠ Cloud verified | βœ… Cloud + Server (v6+) + DC (Jira v8.14+) | ❌ Cloud only | | Auth | ⚠ API token only | βœ… API token / PAT / OAuth 2.0 | βœ… OAuth 2.1 / API token | _Last verified: 2026-06-23. omni-dev and sooperset rows are live-tested β€” a `tools/list` enumeration (omni-dev branch build vs `ghcr.io/sooperset/mcp-atlassian:latest`) plus a live readβ†’writeβ†’read fidelity cycle on a complex page. Atlassian Rovo's server accepts the API token but gates tool **execution** behind an org-admin grant, so its rows combine Atlassian's [Supported tools](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/supported-tools/) docs with the ADF-passthrough reasoning (raw ADF can round-trip, but only if the model echoes it faithfully β€” no deterministic guarantee), not a live run. Refresh quarterly or whenever a release-note search for the comparators flags a relevant change._ ## πŸ“‹ Core Commands ### πŸ€– AI-Powered Commit Improvement (`twiddle`) The star feature - intelligently improve your commit messages with real-time model information display: ```bash # Improve commits with contextual intelligence omni-dev git commit message twiddle 'origin/main..HEAD' --use-context # Process large commit ranges with parallel processing omni-dev git commit message twiddle 'HEAD~20..HEAD' --concurrency 5 # Save suggestions to file for review omni-dev git commit message twiddle 'HEAD~5..HEAD' \ --save-only suggestions.yaml # Auto-apply improvements without confirmation omni-dev git commit message twiddle 'HEAD~3..HEAD' --auto-apply ``` ### πŸ” Analysis Commands ```bash # Analyze commits in detail (YAML output) omni-dev git commit message view 'HEAD~3..HEAD' # Analyze current branch vs main omni-dev git branch info main # Get comprehensive help omni-dev help-all ``` ### πŸš€ AI-Powered PR Creation Create professional pull requests with AI-generated descriptions: ```bash # Generate and create PR with AI-powered description omni-dev git branch create pr # Create PR with specific base branch omni-dev git branch create pr main # Save PR details to file without creating omni-dev git branch create pr --save-only pr-description.yaml # Auto-create without confirmation omni-dev git branch create pr --auto-apply ``` ### πŸ“ Atlassian Integration Read, write, and manage JIRA issues and Confluence pages from the command line: ```bash # Authenticate with Atlassian Cloud omni-dev atlassian auth login # Check authentication status omni-dev atlassian auth status # Fetch a JIRA issue as markdown omni-dev atlassian jira read PROJ-123 # Fetch as raw ADF JSON omni-dev atlassian jira read PROJ-123 --format adf # Push markdown changes back to JIRA omni-dev atlassian jira write PROJ-123 issue.md # Interactive edit: fetch, edit in $EDITOR, push omni-dev atlassian jira edit PROJ-123 # Search issues with JQL omni-dev atlassian jira search --project PROJ --status Open # Create an issue omni-dev atlassian jira create issue.md --project PROJ --summary "Fix bug" # Transition an issue omni-dev atlassian jira transition PROJ-123 "In Progress" # Confluence: read, search, create pages omni-dev atlassian confluence read 12345 omni-dev atlassian confluence search --space ENG --title auth omni-dev atlassian confluence create page.md --space ENG --title "New Page" # Convert markdown to ADF JSON (offline) omni-dev atlassian convert to-adf input.md ``` ### πŸ“Š Datadog Integration (read-only) Authenticate against the Datadog API and query metrics, monitors, dashboards, logs, events, SLOs, hosts, and downtimes. See the [Datadog integration guide](docs/datadog.md) for the full subcommand reference, authentication setup, rate-limit behaviour, and troubleshooting. ```bash # Configure Datadog API credentials (prompts for API key, APP key, and site) omni-dev datadog auth login # Verify the credentials by calling /api/v1/validate omni-dev datadog auth status # Query metrics, monitors, dashboards, logs, and SLOs omni-dev datadog metrics query --query 'avg:system.cpu.user{*}' --from 15m omni-dev datadog monitor list --tags env:prod omni-dev datadog dashboard list omni-dev datadog logs search --filter 'service:api status:error' --from 1h omni-dev datadog slo list --tags team:platform ``` `DATADOG_SITE` defaults to `datadoghq.com`. Other regions (`datadoghq.eu`, `us3.datadoghq.com`, `us5.datadoghq.com`, `ap1.datadoghq.com`, `ddog-gov.com`) are recognised without warning. Environment variables `DATADOG_API_KEY`, `DATADOG_APP_KEY`, `DATADOG_SITE` override the stored settings. For on-prem or proxied installs, set `DATADOG_API_URL` to override the site-derived URL. All Datadog subcommands are also exposed as MCP tools (`datadog_*`) β€” see [docs/mcp.md](docs/mcp.md#datadog-14-tools). For the full guide covering every family with worked examples, see [docs/datadog.md](docs/datadog.md). ### πŸŽ™οΈ Transcript Fetching Pull captions and transcripts from external media platforms. YouTube is the first supported source; the CLI namespace and library are designed so additional sources (Vimeo, podcast RSS, generic VTT/SRT URLs) can be added without restructuring. See [docs/transcript.md](docs/transcript.md) for the full reference and the recipe for adding a new source. ```bash # Fetch captions for a YouTube video as SubRip (default). omni-dev transcript youtube fetch https://www.youtube.com/watch?v=jNQXAC9IVRw # WebVTT to a file, falling through to auto-generated captions if needed. omni-dev transcript youtube fetch jNQXAC9IVRw \ --format vtt --auto --output me-at-the-zoo.vtt # Synthesise a translated track when no native French track exists. omni-dev transcript youtube fetch --lang fr --translate fr # List available caption tracks (manual + auto-generated). omni-dev transcript youtube list-langs # Show video metadata (title, channel, duration, languages). omni-dev transcript youtube info --output json ``` `--format` accepts `srt`, `vtt`, `txt`, or `json`. Locators may be a `watch?v=` URL, a `youtu.be/` short URL, a `/shorts/` or `/embed/` URL, or a bare 11-character video ID. Age-gated and login-required videos surface as a typed `PlayabilityRefused` error carrying YouTube's status code rather than a generic HTTP failure. ### 🌐 Browser Bridge Drive HTTP requests **through an authenticated browser tab**. When you are investigating internal services (Grafana/Loki … ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source β€” we do not rehost the code. - **Author:** [rust-works](https://github.com/rust-works) - **Source:** [rust-works/omni-dev](https://github.com/rust-works/omni-dev) - **License:** BSD-3-Clause Install and usage instructions live in the source repository linked above. ## Pricing - **Free** β€” Free ## Security capabilities Automated source analysis of v0.1.0 β€” what this tool can access: - **Network access:** yes - **Filesystem access:** no - **Shell / process execution:** yes - **Environment & secrets:** yes - **Dynamic code execution:** no *"Yes" means the capability is present in the source β€” more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** β€” security scan: flagged β€” Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-rust-works-omni-dev - Seller: https://agentstack.voostack.com/s/rust-works - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack β€” the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.