vibie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VIBIE_API_BASE | No | Override for local dev (e.g. http://localhost:3000) | https://vibie.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vibie_create_siteA | Create 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_siteA | Update 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_sitesA | List 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_siteA | Get metadata for a single Vibie site by slug. Returns name, category, URL, visibility, like count, timestamps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: create, get (single), list (all), and update. No overlap or ambiguity between them.
All tools follow a consistent 'vibie_verb_noun' snake_case pattern. The prefix and structure are predictable and uniform.
With 4 tools, the server is well-scoped for managing Vibie sites. Each tool earns its place without redundancy or insufficiency.
The set covers create, read (single and list), and update, which are core operations. Only missing delete, which is a minor gap.