Ext Ops Panel
Open dashboard
Comparison

PostQuickAI vs Glif

PostQuickAI is an MCP server published by www.postquick.ai. Marketplaces we read that list it: 1 (Official MCP Registry). 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-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
MarketplacePostQuickAIGlif
Official MCP Registry Listed
Version: 0.1.5
Downloads/month (npm): 297
Downloads/week (npm): 68
Not marked · First seen
Listed
Version: 1.0.1
Forks (GitHub): 32
Stars (GitHub): 218
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:3f93ddceeb99
Forks (GitHub): 32
Pulls (Docker Hub): 20 171
Stars (Docker Hub): 2
Stars (GitHub): 218
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

PostQuickAI vs Glif
FactPostQuickAIGlif
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)No figure on GitHub218
Pulls (Docker Hub) (differs)No figure on Docker Hub20 171
Forks (GitHub) (differs)No figure on GitHub32
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.postquick.ai/api/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declares (differs)Not published10
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 1
Parts of the bundle (differs)Not a bundle11
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/glifxyz/glif-mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-182026-10-11
Endpoint at the last check (differs)Status out of date: last check 35 h ago returned HTTP 401Status out of date: last check 45 h ago returned HTTP 405

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

PostQuickAI

In its own words, on Official MCP Registry:

Draft, schedule and review social posts on X, LinkedIn, Instagram, TikTok, YouTube and more.

Glif

In its own words, on Official MCP Registry:

Generate images, video, and audio with Glif's media-generation agent

How to run each

PostQuickAI As a remote MCP server

Claude Code
claude mcp add --transport http postquickai https://www.postquick.ai/api/mcp

Requires: POSTQUICKAI_API_KEY (secret)

Glif As a remote MCP server

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

Commands 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 PostQuickAI publish no list of tools, so we do not compare tools.

Settings each asks for

Only PostQuickAI asks for

  • POSTQUICKAI_API_KEY (secret)

Only Glif asks for

  • GLIF_API_TOKEN (secret)
  • GLIF_IDS
  • IGNORE_SAVED_GLIFS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: PostQuickAI · What it can do: Glif · Compare two other plugins

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. 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.

Where the data comes from: how the catalog is built