spillway-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOCAL_GPU_PROFILE | No | Hardware preset for local GPU inference. Valid values: 8gb_vram, 12gb_vram, 24gb_vram_or_mac_unified. | |
| LOCAL_LLM_BASE_URL | No | Base URL for the local OpenAI-compatible LLM server (e.g., http://127.0.0.1:11434/v1 for Ollama). | |
| LOCAL_OLLAMA_MODEL | No | Model name to use with Ollama for local GPU inference (e.g., qwen2.5-coder:14b). | |
| AGY_GIT_REPORT_ONLY | No | Set to 1 to restrict git operations to read-only reporting. | |
| AGY_MAX_CONCURRENCY | No | Maximum number of concurrent Antigravity (cloud) subagent tasks. Default is 1. | 1 |
| AGY_NO_SELF_BOOTSTRAP | No | Set to 1 to prevent the server from automatically bootstrapping configuration (e.g., modifying .mcp.json). | |
| LOCAL_GPU_CONCURRENCY | No | Maximum number of concurrent local GPU tasks. Default is 1. | 1 |
| AGY_DENY_SKIP_PERMISSIONS | No | Set to 1 to disallow skipping permission checks. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agy_delegate_researchA | Delegate deep read-only codebase research, cross-module architectural analysis, bug root-cause tracing, or security verification to Google Antigravity CLI (agy) using verified Gemini 3.8 Flash or Gemini 4 Argon models in --mode=plan. WHEN TO USE: Complex multi-file reasoning or architectural audits across 5–30+ files after initial scouting. DO NOT USE FOR: Simple signature, import, or line-number extraction on known files (use |
| agy_spawn_swarmA | Dispatch multiple read-only Antigravity subagents using gemini-3.8-flash-low or gemini-3.8-flash-medium across strictly disjoint directory partitions. WHEN TO USE: Exploring multiple independent subsystems or directories in a single turn. DO NOT USE FOR: Single-directory research (use |
| agy_delegate_editA | Delegate complex multi-file code modifications or cross-module refactoring to Antigravity (agy) in --mode=accept-edits. WHEN TO USE: Coordinated edits across multiple existing files requiring Gemini Argon/Flash reasoning. DO NOT USE FOR: Generating a single standalone boilerplate, DTO, schema, or unit test file (use |
| agy_session_followupA | Resume an existing Antigravity conversation ID (--conversation ) so previously loaded files remain in context cache, automatically compacting the session if context usage exceeds 80%. WHEN TO USE: Multi-turn follow-up questions on an existing Session ID returned by a prior |
| agy_configure_workspaceA | Update workspace environment configuration and Antigravity IDE Visual HUD settings. Auto-detects project toolchains (.venv, node_modules/.bin), registers monorepo directories (--add-dir), injects environment variables, optionally syncs .vscode/settings.json, and attaches or launches the Antigravity IDE window. WHEN TO USE: Only when configuring custom virtualenv/monorepo paths or toggling IDE Visual HUD attachment. DO NOT USE FOR: Read-only status or quota checks (use |
| agy_statusA | Inspect current system health, Gemini 5-hour/weekly quota windows, Local GPU VRAM availability ( |
| local_file_scoutA | ZERO-TRUST MEMORY TOOL: Read repository files directly from disk on the server side and use the Local GPU LLM (0x cloud quota) as a strict forensic disk-evidence extractor. Outputs verbatim signatures, imports, and logic with exact 1-based |
| local_exec_and_triageA | Execute allow-listed test, build, typecheck, or lint commands (pytest, npm test, npx tsc, cargo check, go test) in a managed subprocess with Windows process-tree kill protection ( |
| local_draft_leaf_codeA | Draft standalone leaf-node boilerplate, unit test files, DTOs, or schemas on disk using the Local GPU LLM (0x cloud quota). Reads |
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 9 tools
The descriptions include explicit routing guidance with 'WHEN TO USE' and 'DO NOT USE FOR' clauses, so boundaries between research, scouting, editing, drafting, and execution are mostly clear. There is still inherent conceptual overlap between agy_delegate_research/local_file_scout and agy_delegate_edit/local_draft_leaf_code, but the workflow distinctions make misselection unlikely.
All tools use snake_case with consistent agy_ and local_ prefixes that reflect execution tier. The action portion varies between verb-led (delegate_research, spawn_swarm, configure_workspace) and noun-led (status, session_followup, file_scout), so it is not a perfect verb_noun pattern, but it remains predictable and readable.
Nine tools is well-scoped for a coding orchestration server. Each tool maps to a distinct orchestration responsibility: research, swarm dispatch, editing, session continuation, configuration, status, disk scouting, execution, and leaf-file drafting.
The surface covers the core lifecycle of delegated research, editing, follow-up, local scouting, drafting, execution, status, and configuration. Minor gaps remain around explicit session cancellation/cleanup or quota reset, but agents can work around them using status and follow-up tools.