Vibie MCP vs Telbase
A side-by-side look at the Vibie MCP and Telbase MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TelbaseCloud PlatformsDeploy any web project with one command. AI-native platform with self-healing feedback.37FairAuth: not declaredVerdict: choose Vibie MCP for cloud platforms work as a local process; choose Telbase for cloud platforms. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Vibie MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
VIBIE_API_BASE. - You want tools like
vibie_create_site, vibie_update_site, vibie_list_sites.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Telbase | |
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 59/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | VIBIE_API_BASE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | — |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Vibie MCP | View Telbase |
Tools & capabilities
Vibie MCP tools 4
vibie_create_siteCreate a NEW Vibie site by uploading a local folder. Use this when the user wants to publish a brand new site, or when no .vibie/site.json marker exists in the folder. Vibie hosts static HTML/CSS/JS at a permanent URL like my-site-a3f9.vibie.page. Auto-creates a .vibie/site.json marker in the folder for future updates.vibie_update_siteUpdate an existing Vibie site with new content from a local folder. Use this when the user wants to re-deploy or push changes to an already-published site. If .vibie/site.json marker exists in the folder, the slug is read automatically; otherwise pass slug explicitly. Same URL, new content.vibie_list_sitesList all sites owned by the current Vibie user. Returns slug, display name, category, URL, visibility, and last update time. Use this to discover what sites the user already has, e.g. before update.vibie_get_siteGet metadata for a single Vibie site by slug. Returns name, category, URL, visibility, like count, timestamps.
Telbase tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Vibie MCP
{
"mcpServers": {
"shdomi8599-vibie-mcp": {
"command": "npx",
"args": [
"-y",
"vibie-mcp"
],
"env": {
"VIBIE_API_BASE": "YOUR_VIBIE_API_BASE_HERE"
}
}
}
}
Telbase
No confirmed install command for Telbase yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Vibie MCP is categorized under Cloud Platforms and uses a local stdio subprocess. Telbase belongs to Cloud Platforms and uses an install path we have not confirmed yet. Pick Vibie MCP for cloud platforms work and Telbase for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Telbase has no confirmed install command yet — follow its own setup instructions.
Vibie MCP is listed as free. Auth: oauth 2.0. Telbase has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add shdomi8599-vibie-mcp and telbase as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Vibie MCP has a quality signal of 59/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Telbase has 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.