local-vibes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_VIBES_LANE | No | Default sticky-session id, sent as the standard OpenAI user field (per-call lane overrides) | |
| LOCAL_VIBES_MODEL | No | Model name on that endpoint | qwen3-coder:30b |
| LOCAL_VIBES_API_KEY | No | Sent as the key; local servers ignore it | not-needed |
| LOCAL_VIBES_BASE_URL | No | OpenAI-compatible endpoint | http://localhost:11434/v1 |
| LOCAL_VIBES_MAX_ITERS | No | Max model↔tool round-trips per task | 25 |
| LOCAL_VIBES_ALLOW_BASH | No | 0 disables the run_bash tool entirely | 1 |
| LOCAL_VIBES_EXTRA_BODY | No | JSON object merged into every request body — superset passthrough | {} |
| LOCAL_VIBES_LANE_HEADER | No | Optional: also send the lane under this custom header (opt-in; for header-routing servers) | |
| LOCAL_VIBES_TEMPERATURE | No | Default sampling temperature (per-call temperature overrides) | 0.1 |
| LOCAL_VIBES_BASH_TIMEOUT | No | Per-command timeout (seconds) | 120 |
| LOCAL_VIBES_MAX_CONCURRENCY | No | Cohort width — concurrent delegate loops offered to the backend | 8 |
| LOCAL_VIBES_TOOL_RESULT_CAP | No | Max chars of any tool result fed back to the model | 12000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegateA | Delegate a self-contained coding or research task to a LOCAL model running in its own sandboxed agent loop. USE PROACTIVELY to offload grunt work — codebase searches, boilerplate, mechanical multi-file edits, test scaffolding — instead of doing it inline. The subagent reads/edits files and runs shell commands confined to |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/OpenSourceWTF/local-vibes'
If you have feedback or need assistance with the MCP directory API, please join our Discord server