Ext Ops Panel
Open dashboard
Comparison

usectl vs mtdt — Salesforce DevOps

usectl is a plugin bundle for AI coding tools published by syst3mctl. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). mtdt — Salesforce DevOps is an MCP server published by mtdt.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplaceusectlmtdt — Salesforce DevOps
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.2
Forks (GitHub): 0
Stars (GitHub): 0
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

usectl vs mtdt — Salesforce DevOps
Factusectlmtdt — Salesforce DevOps
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (@usectl/mcp-server)Remote server (mcp.mtdt.io)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/syst3mctl/usectl-plugingithub.com/mtdt-io/mcp
Changes in the last 7 days (differs)01
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

usectl

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

Deploy and manage full-stack projects on usectl — a managed Kubernetes platform that turns a GitHub repo into a live HTTPS app with PostgreSQL, S3 storage, and automatic SSL. Includes deployment skill with full lifecycle knowledge, MCP server integration for direct API access, and slash commands (/deploy, /status, /logs) for quick operations. One prompt deploys your entire project.

mtdt — Salesforce DevOps

In its own words, on Official MCP Registry:

mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)

How to run each

usectl As a Claude Code plugin

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

mtdt — Salesforce DevOps As a remote MCP server

Claude Code
claude mcp add --transport http mtdt https://mcp.mtdt.io

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 mtdt — Salesforce DevOps publish no settings it asks for, so we do not compare settings.

What it can do: usectl · What it can do: mtdt — Salesforce DevOps · 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