Iaptic vs Teamup Calendar MCP by usefulapi
Iaptic is an MCP server published by iaptic. Marketplaces we read that list it: 1 (Docker MCP Catalog). Teamup Calendar MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  Iaptic |   Teamup Calendar MCP by usefulapi |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7f86e3becb71 Forks (GitHub): 6 Pulls (Docker Hub): 16 387 Stars (Docker Hub): 0 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | Iaptic | Teamup Calendar MCP by usefulapi |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 16 387 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/iaptic) | Remote server (teamup-calendar.usefulapi.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 17 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/iaptic/mcp-server-iaptic | github.com/m190/usefulapi-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 35 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
Iaptic
Model Context Protocol server for interacting with iaptic.
Teamup Calendar MCP by usefulapi
Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.
How to run each
Iaptic As a local MCP server: Docker image
claude mcp add --env "IAPTIC_API_KEY=<YOUR_IAPTIC_API_KEY>" --transport stdio iaptic -- docker run -i --rm -e IAPTIC_API_KEY mcp/iapticRequires: IAPTIC_API_KEY (secret)
Teamup Calendar MCP by usefulapi As a remote MCP server
claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Teamup Calendar MCP by usefulapi has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Teamup Calendar MCP by usefulapi publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Teamup Calendar MCP by usefulapi publish no settings it asks for, so we do not compare settings.
What it can do: Iaptic · What it can do: Teamup Calendar MCP by usefulapi · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.