post-bridge vs Glif
post-bridge is a plugin bundle for AI coding tools published by post-bridge-hq. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 |  post-bridge |   Glif |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 3 Stars (GitHub): 17 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 36 Stars (GitHub): 215 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 36 Pulls (Docker Hub): 19 761 Stars (Docker Hub): 2 Stars (GitHub): 215 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 | post-bridge | Glif |
|---|---|---|
| Marketplaces that list it (differs) | 2 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 17 (worse) | 215 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 19 761 |
| Forks (GitHub) (differs) | 3 (worse) | 36 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (www.post-bridge.com/api/mcp/mcp) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 10 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 4 | 11 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/post-bridge-hq/agent-mode | github.com/glifxyz/glif-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | Responded 4 days ago |
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
post-bridge
Post to Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Pinterest, Threads, and Bluesky via Post Bridge API
Glif
Generate images, video, and audio with Glif's media-generation agent
How to run each
post-bridge As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install post-bridge@claude-communityGlif As a remote MCP server
claude mcp add --transport http glif https://glif.app/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of post-bridge publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of post-bridge publish no settings it asks for, so we do not compare settings.
What it can do: post-bridge · What it can do: Glif · 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 public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.