Ext Ops Panel
Open dashboard
Comparison

jobctl vs jobd

jobctl is an MCP server published by DmytroRybka. Marketplaces we read that list it: 1 (Official MCP Registry). jobd is an MCP server published by musharna. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplacejobctljobd
Official MCP Registry Listed
Version: 0.5.1
No figure published
Not marked · First seen
Listed
Version: 0.5.57
Downloads/month (PyPI): 1 321
Downloads/week (PyPI): 184
Forks (GitHub): 0
Stars (GitHub): 5
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

jobctl vs jobd
Factjobctljobd
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub5
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-11-09
Where it runs (differs)Remote server (app.jobctl.app/mcp)On your machine (jobd)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/musharna/jobd
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 43 h ago returned HTTP 405no remote endpoint we check

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

jobctl

In its own words, on Official MCP Registry:

Job application tracker for developers - AI agents write over MCP, you review in a dashboard.

jobd

In its own words, on Official MCP Registry:

Self-hostable GPU-aware job broker: submit, route by VRAM, babysit jobs across machines via MCP.

How to run each

jobctl As a remote MCP server

Claude Code
claude mcp add --transport http jobctl https://app.jobctl.app/mcp

jobd As a local MCP server: PyPI package

Claude Code
claude mcp add --env "JOBD_API_TOKEN=<YOUR_JOBD_API_TOKEN>" --transport stdio jobd -- uvx --from "jobd[mcp]" jobd-mcp jobd

Requires: JOBD_API_TOKEN (secret)

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

Only jobctl has a remote endpoint we check. How we check endpoints

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

What it can do: jobctl · What it can do: jobd · Compare two other plugins

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