Ext Ops Panel
Open dashboard
Comparison

Google Calendar vs io.github.chrischall/splitwise-mcp

Google Calendar is a plugin bundle for AI coding tools published by OpenAI. Marketplaces we read that list it: 1 (Codex: openai-curated (openai/plugins)). io.github.chrischall/splitwise-mcp is an MCP server published by chrischall. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
MarketplaceGoogle Calendario.github.chrischall/splitwise-mcp
Codex: openai-curated (openai/plugins) Listed
Version: 1.2.6
Forks (GitHub): 963
Stars (GitHub): 7 415
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.3.1
Downloads/month (npm): 4 222
Downloads/week (npm): 1 119
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

Google Calendar vs io.github.chrischall/splitwise-mcp
FactGoogle Calendario.github.chrischall/splitwise-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 415 (better)1 (worse)
Forks (GitHub) (differs)963 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (calendarmcp.googleapis.com/mcp/v1)On your machine (splitwise-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle22
LicenceMITMIT
Repository (differs)github.com/openai/pluginsgithub.com/chrischall/splitwise-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

Google Calendar

In its own words, on Codex: openai-curated (openai/plugins):

Connect Google Calendar for scheduling, availability, daily briefs, and event management.

io.github.chrischall/splitwise-mcp

In its own words, on Official MCP Registry:

Splitwise expense and group management for Claude — shared expenses, settle up, friends

How to run each

Google Calendar As a Codex plugin

Codex
codex plugin marketplace add openai/plugins

io.github.chrischall/splitwise-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "SPLITWISE_API_KEY=<YOUR_SPLITWISE_API_KEY>" --transport stdio splitwise-mcp -- npx -y splitwise-mcp

Requires: SPLITWISE_API_KEY (secret)

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 Google Calendar publish no settings it asks for, so we do not compare settings.

What it can do: Google Calendar · What it can do: io.github.chrischall/splitwise-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/openai/plugins/blob/HEAD/.agents/plugins/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.

Where the data comes from: how the catalog is built