Tempmd MCP vs Vibie MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Tempmd MCP vs Vibie MCP
In-depth architectural comparison of the Tempmd MCP and Vibie MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Tempmd MCP
Cloud Platforms · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Vibie MCP
Cloud Platforms · Local stdio
Quality: 52/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Tempmd MCP if you need specialized Cloud Platforms tools running via a local process. Choose Vibie MCP if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Tempmd MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: One stable, canonical URL per artifact that updates in place, Supports HTML, Markdown, CSV, and Mermaid artifacts, 7-day active window that resets on update; 7-day restore grace period after expiry.
Publish agent-made artifacts (HTML, Markdown, CSV, Mermaid) to temp.md — one stable public link that updates in place. Anonymous publish with no API key, activity-based expiry with restore. Install: npx tempmd-mcp.
Deploy static HTML folders to permanent vibie.page URLs in seconds. One-line auto-install (npx vibie-mcp setup) wires up Claude Desktop and Cursor, OAuth device-flow auth, automatic folder marker for repeat deploys without re-typing slugs.
Category & Scope
Tools & Capabilities Breakdown
Tempmd MCP Tools (5)
One stable, canonical URL per artifact that updates in place
Supports HTML, Markdown, CSV, and Mermaid artifacts
7-day active window that resets on update; 7-day restore grace period after expiry
No account or API key required — anonymous publishing by default
Remote (10 MiB/20 files) or local stdio (50 MiB/100 files) transport
Vibie MCP Tools (4)
vibie_create_site
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Tempmd MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Vibie MCP belongs to Cloud Platforms using local stdio subprocess. Select Tempmd MCP when you need capabilities focused on cloud platforms and Vibie MCP when you require tools for cloud platforms.