ELSHWORK Agent Network vs AgentTasker MCP Server
ELSHWORK Agent Network is an MCP server published by elshwork.com. Marketplaces we read that list it: 1 (Official MCP Registry). AgentTasker MCP Server is an MCP server published by S3bRR. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
| Marketplace |  ELSHWORK Agent Network |  AgentTasker MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (PyPI): 91 Downloads/week (PyPI): 33 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
| Fact | ELSHWORK Agent Network | AgentTasker MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (elshwork.com/api/agent/v1/mcp) | On your machine (agent-tasker-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/s3brr/agent-tasker-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (3 days ago) | no 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
ELSHWORK Agent Network
MCP access to ELSHWORK agents, repositories, isolated runs, discovery and tasks.
AgentTasker MCP Server
Minimal stdio MCP server for parallel task execution by AI agents.
How to run each
ELSHWORK Agent Network As a remote MCP server
claude mcp add --transport http agent-network https://elshwork.com/api/agent/v1/mcpAgentTasker MCP Server As a local MCP server: PyPI package
claude mcp add --transport stdio agent-tasker-mcp -- uvx agent-tasker-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ELSHWORK Agent Network 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
Neither one's marketplaces publish the settings it asks for.
What it can do: ELSHWORK Agent Network · What it can do: AgentTasker MCP Server · 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.