Syncline MCP Server (Python) vs Temporal Cortex Calendar MCP
Syncline MCP Server (Python) is an MCP server published by kekwanu.com. Marketplaces we read that list it: 1 (Official MCP Registry). Temporal Cortex Calendar MCP is an MCP server published by billylui. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Syncline MCP Server (Python) |  Temporal Cortex Calendar MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.35 Downloads/month (PyPI): 340 Downloads/week (PyPI): 81 Not marked · First seen |
Listed Version: 0.5.0 Downloads/month (npm): 360 Downloads/week (npm): 68 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 | Syncline MCP Server (Python) | Temporal Cortex Calendar MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 13 |
| Forks (GitHub) (differs) | No figure on GitHub | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (syncline-mcp-server) | On your machine (@temporal-cortex/cortex-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 15, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/kekwanulabs/syncline | github.com/billylui/temporal-cortex-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Syncline MCP Server (Python)
Syncline MCP Server (Python) - AI-powered meeting scheduling with intelligent auto-scheduling
Temporal Cortex Calendar MCP
12 deterministic calendar tools — temporal context, scheduling, availability, and booking
How to run each
Syncline MCP Server (Python) As a local MCP server: PyPI package
claude mcp add --env "SYNCLINE_API_KEY=<YOUR_SYNCLINE_API_KEY>" --transport stdio syncline-mcp-server-python -- uvx syncline-mcp-serverRequires: SYNCLINE_API_KEY (secret)
Temporal Cortex Calendar MCP As a local MCP server: npm package
claude mcp add --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "MICROSOFT_CLIENT_SECRET=<YOUR_MICROSOFT_CLIENT_SECRET>" --transport stdio temporal-cortex-mcp -- npx -y @temporal-cortex/cortex-mcpRequires: GOOGLE_CLIENT_SECRET (secret), MICROSOFT_CLIENT_SECRET (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
Only Syncline MCP Server (Python) asks for
SYNCLINE_API_KEY (secret)
Only Temporal Cortex Calendar MCP asks for
ALLOWED_ORIGINSGOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET (secret)GOOGLE_OAUTH_CREDENTIALSHTTP_HOSTHTTP_PORTLOCK_TTL_SECSMICROSOFT_CLIENT_IDMICROSOFT_CLIENT_SECRET (secret)OAUTH_REDIRECT_PORTREDIS_URLSTEMPORAL_CORTEX_TELEMETRY
Show the remaining 3
TENANT_IDTIMEZONEWEEK_START
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Syncline MCP Server (Python) · What it can do: Temporal Cortex Calendar MCP · Compare two other plugins
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.