Vibe MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | MCP server host | 0.0.0.0 |
| MCP_PORT | No | MCP server port | 9000 |
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | INFO |
| MCP_TRANSPORT | No | MCP transport (stdio, sse) | stdio |
| VIBE_BASE_URL | Yes | Vibe API base URL | |
| ENABLE_METRICS | No | Enable metrics collection | true |
| VIBE_MAX_RETRIES | No | Max retry attempts for failed requests | 3 |
| VIBE_ACCESS_TOKEN | Yes | Bearer token for authentication | |
| ENABLE_HEALTH_CHECK | No | Enable health check tool | true |
| VIBE_RETRY_BACKOFF_SECONDS | No | Initial backoff time (exponential) | 0.5 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_project_listC | Retrieve all projects from the Vibe system |
| create_repoC | Create a new repository in the Vibe system |
| create_bucketC | Create a new bucket in the Vibe system |
| get_activityC | Get activity information from the Vibe system |
| get_codeC | Get code information from the Vibe system |
| health_checkA | Check the health and connectivity of the Vibe system |
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 6 tools
Each tool targets a distinct resource or action: bucket creation, repo creation, activity retrieval, code retrieval, project listing, and health check. No overlap in purpose.
Most tools follow a consistent verb_noun pattern (e.g., create_bucket, get_activity), but health_check is noun_verb, creating a minor inconsistency.
With 6 tools, the set feels well-scoped for a system managing buckets, repos, projects, and health. Not too few or too many.
Significant gaps exist: there are create operations for buckets and repos but no corresponding list, get, update, or delete operations for these resources. The get operations only cover activity, code, and a project list.