agent-blog vs Blawgy
agent-blog is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
agent-blog is a plugin bundle for AI coding tools published by Agent Blog. No marketplace we read lists it any more. Blawgy is an MCP server published by blawgy.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Blawgy | |
|---|---|---|
| Community marketplace dogacel/agent-blog | Removed on 2026-10-26 Version: 0.2.5 Forks (GitHub): 0 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 3 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 | agent-blogno longer listed · | Blawgy |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 10 | 3 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (app.blawgy.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dogacel/agent-blog | github.com/adamgusky/blawgy-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 44 h ago returned HTTP 405 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of agent-blog
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Turn your daily dev activity into build-in-public posts. Scans git repos, generates human-sounding posts, schedules future posts, and auto-publishes to Threads.
-
Inki — research, write, review, submit your docs. A Claude Code plugin encapsulating the Strapi documentation toolkit.
-
Dual-mode blog publishing assistant. Ship new posts via 8-step lifecycle OR audit existing posts. Wraps AgriciDaniel/claude-blog.
-
📚 FAOS Technical Writer — Technical Documentation Specialist + Knowledge Curator
-
Blog post creation - project logs, technical write-ups, personal documentation
-
Tools for bootstrapping content creation such as blog posts and conference talks
What each says it does
agent-blog
Claude Code plugin that automatically writes technical blog posts from your coding sessions
Blawgy
Research keywords, plan, write, update and publish SEO blog posts on your site from any agent.
How to run each
agent-blog
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Blawgy As a remote MCP server
claude mcp add --transport http blawgy https://app.blawgy.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Blawgy 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: agent-blog · What it can do: Blawgy · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.