web-ctl vs HTTP
web-ctl is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). HTTP is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: e00f409 No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (npm): 187 Downloads/week (npm): 31 Forks (GitHub): 0 Stars (GitHub): 1 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 | web-ctl | HTTP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@abhishekmcp/http) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Parts of the bundle (differs) | Not published | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/agent-sh/web-ctl | github.com/abhishekkumar2021/mcp-suite |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-12 | 2026-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
web-ctl
Browser automation toolkit for AI agents — navigate, authenticate, and interact with web pages through a single CLI. Agents drive headless browsers to fill forms, click buttons, read content, and capture screenshots; when login or CAPTCHA is required, the browser opens for the human, the human completes auth, and control returns to headless mode (auth handoff). Persistent sessions survive across CLI invocations so the agent doesn't need to log in repeatedly. Built-in prompt-injection defense for content read from pages. Designed for tasks where the agent needs to interact with a real web app — testing flows, scraping behind a login, automating internal dashboards.
HTTP
HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.
How to run each
web-ctl As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install web-ctl@claude-community
HTTP As a local MCP server: npm package
claude mcp add --env "HTTP_ALLOW_HOSTS=<YOUR_HTTP_ALLOW_HOSTS>" --transport stdio http -- npx -y @abhishekmcp/http
Requires: HTTP_ALLOW_HOSTS
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 web-ctl publish no settings it asks for, so we do not compare settings.
What it can do: web-ctl · What it can do: HTTP · 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.