io.github.PhilflowIO/dav-mcp vs PPT.AI Developer API
io.github.PhilflowIO/dav-mcp is an MCP server published by PhilflowIO. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). PPT.AI Developer API is an MCP server published by zenlee123. 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
| Marketplace |  io.github.PhilflowIO/dav-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 5.0.0 Downloads/month (npm): 2 309 Downloads/week (npm): 208 Forks (GitHub): 17 Stars (GitHub): 40 Not marked · First seen |
Listed Version: 1.0.1 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 5.0.0 Downloads/month (npm): 2 309 Downloads/week (npm): 208 Forks (GitHub): 17 Stars (GitHub): 40 Not marked · First seen |
Not listed |
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 | io.github.PhilflowIO/dav-mcp | PPT.AI Developer API |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 40 | No figure on GitHub |
| Forks (GitHub) (differs) | 17 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (dav-mcp) | Remote server (developer.ppt.ai/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 10, secrets among them: 3 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/philflowio/dav-mcp | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-17 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
io.github.PhilflowIO/dav-mcp
AI-orchestrated calendars, contacts & tasks across any DAV platform. 27 tools, field-agnostic.
PPT.AI Developer API
Create, edit, export and manage presentations. Requires a paid PPT.AI API merchant account.
How to run each
io.github.PhilflowIO/dav-mcp As a local MCP server: npm package
claude mcp add --env "CALDAV_PASSWORD=<YOUR_CALDAV_PASSWORD>" --env "CALDAV_SERVER_URL=<YOUR_CALDAV_SERVER_URL>" --env "CALDAV_USERNAME=<YOUR_CALDAV_USERNAME>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GOOGLE_REFRESH_TOKEN=<YOUR_GOOGLE_REFRESH_TOKEN>" --transport stdio dav-mcp -- npx -y dav-mcpRequires: CALDAV_PASSWORD (secret), CALDAV_SERVER_URL, CALDAV_USERNAME, GOOGLE_CLIENT_SECRET (secret), GOOGLE_REFRESH_TOKEN (secret)
PPT.AI Developer API As a remote MCP server
claude mcp add --transport http ppt-ai-api https://developer.ppt.ai/api/mcp --header "Api-Secret: <YOUR_API_SECRET>"Requires: Api-Secret header
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 PPT.AI Developer API publish no settings it asks for, so we do not compare settings.
What it can do: io.github.PhilflowIO/dav-mcp · What it can do: PPT.AI Developer API · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.