Ext Ops Panel
Open dashboard
Comparison

WakeWire vs Connected Apps

WakeWire is a plugin bundle for AI coding tools published by Glenn Calleja Frendo. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Connected Apps is an MCP server published by pollinations. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
MarketplaceWakeWireConnected Apps
Community marketplace glenncalleja/wakewire Listed
Version: 0.1.0
Forks (GitHub): 4
Stars (GitHub): 11
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 1 204
Stars (GitHub): 5 227
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

WakeWire vs Connected Apps
FactWakeWireConnected Apps
Marketplaces that list it11
Stars (GitHub) (differs)11 (worse)5 227 (better)
Forks (GitHub) (differs)4 (worse)1 204 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (wakewire)Remote server (gen.pollinations.ai/mcp/composio)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/glenncalleja/wakewiregithub.com/pollinations/pollinations
Changes in the last 7 days (differs)20
First seen (differs)2026-10-192026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 h ago, requires a key

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

WakeWire

In its own words, on Community GitHub marketplaces:

Break the loop — deliver GitHub, Gmail, Slack, and any webhook's events (Linear, Sentry, ClickUp) into local Codex threads in near real time, configured conversationally.

Connected Apps

In its own words, on Official MCP Registry:

Read Gmail, search GitHub, update Sheets, and post to Slack through Composio.

How to run each

WakeWire As a Codex plugin

Codex
codex plugin marketplace add glenncalleja/wakewire

Connected Apps As a remote MCP server

Claude Code
claude mcp add --transport http composio https://gen.pollinations.ai/mcp/composio --header "Authorization: Bearer <YOUR_API_KEY>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Connected Apps 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: WakeWire · What it can do: Connected Apps · 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.

Where the data comes from: how the catalog is built