Ext Ops Panel
Open dashboard
Comparison

one-workflow vs io.github.SurgeX-Labs/awx-mcp-server

one-workflow is a plugin bundle for AI coding tools published by ATreep. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.SurgeX-Labs/awx-mcp-server is an MCP server published by SurgeX-Labs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceone-workflowio.github.SurgeX-Labs/awx-mcp-server
Claude Code: claude-plugins-community Listed
Version: v260627-000521
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.2
Downloads/month (PyPI): 320
Downloads/week (PyPI): 97
Forks (GitHub): 13
Stars (GitHub): 14
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

one-workflow vs io.github.SurgeX-Labs/awx-mcp-server
Factone-workflowio.github.SurgeX-Labs/awx-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)14 (better)
Forks (GitHub) (differs)0 (worse)13 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (awx-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 2
Parts of the bundle (differs)1Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/atreep/one-workflowgithub.com/surgex-labs/awx-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

one-workflow

In its own words, on Claude Code: claude-plugins-community:

A high-layer DevOps workflow for beginners, based on Everything-Claude-Code. One Workflow allows you to build a mature software project with simply several commands.

io.github.SurgeX-Labs/awx-mcp-server

In its own words, on Official MCP Registry:

Control AWX/Ansible Tower through natural language - 49 tools for automation

How to run each

one-workflow As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install one-workflow@claude-community

io.github.SurgeX-Labs/awx-mcp-server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "AWX_BASE_URL=<YOUR_AWX_BASE_URL>" --env "AWX_PASSWORD=<YOUR_AWX_PASSWORD>" --env "AWX_TOKEN=<YOUR_AWX_TOKEN>" --transport stdio awx-mcp-server -- uvx awx-mcp-server

Requires: AWX_BASE_URL, AWX_PASSWORD (secret), AWX_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of one-workflow publish no settings it asks for, so we do not compare settings.

What it can do: one-workflow · What it can do: io.github.SurgeX-Labs/awx-mcp-server · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built