firepass-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIREPASS_MODEL | No | Model ID | accounts/fireworks/routers/kimi-k2p6-turbo |
| FIREPASS_MAX_READ | No | Max chars per file read | 100000 |
| FIREWORKS_API_KEY | Yes | Fireworks AI API key | |
| FIREPASS_MAX_OUTPUT | No | Max chars per tool result | 50000 |
| FIREPASS_BASH_TIMEOUT | No | Shell command timeout (seconds) | 60 |
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 |
|---|---|
| firepass_workerA | Run a coding task with FirePass worker (Kimi K2.6 Turbo + tool loop). The worker can read/write/edit files, run bash, search with ripgrep/ast-grep/jq, and iterate autonomously until done. Args: prompt: The coding task. cwd: Working directory to sandbox file access to. context: Optional file contents, errors, or specs to pre-load. max_iterations: Max tool-call rounds (default 60). |
| firepass_researcherA | Run a research task with FirePass researcher (Kimi K2.6 Turbo + read-only tool loop). The researcher can read files, search with ripgrep/ast-grep/jq/glob, and iterate autonomously. No file writes or shell commands. Args: prompt: Research question or analysis task. cwd: Working directory to sandbox file access to. context: Optional file contents, docs, or code to pre-load. max_iterations: Max tool-call rounds (default 60). |
| firepass_reviewerA | Run a code review with FirePass reviewer (Kimi K2.6 Turbo + read-only tool loop). The reviewer can read files, search with ripgrep/ast-grep/jq/glob, and iterate autonomously. No file writes or shell commands. Returns structured review: blocking issues, suggestions, and what's done well. Args: prompt: What to review — files, a diff, a PR description, or a specific concern. cwd: Working directory to sandbox file access to. context: Optional diff, file contents, or PR description to pre-load. max_iterations: Max tool-call rounds (default 60). |
| firepass_trioA | Run a full FirePass trio: research → implement → review → (fix loop). Args: prompt: The coding task. cwd: Working directory to sandbox file access to. context: Optional file contents, errors, or specs to pre-load. max_iterations: Max tool-call rounds per sub-agent (default 60). max_review_rounds: Max worker+reviewer fix rounds (default 2). |
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 maps to a distinct agent role: researcher is read-only analysis, reviewer is read-only code review with structured output, worker can write files and run commands, and trio orchestrates the full pipeline. The descriptions make the boundaries clear despite researcher and reviewer sharing a read-only tool loop.
All tools follow the same firepass_<role> naming convention with single-word role identifiers. The pattern is immediately predictable and there are no mixed styles or vague generic verbs.
Four tools is well-scoped for this server: it exposes exactly the three FirePass agent modes plus the combined trio workflow. Each tool earns its place and the count feels neither thin nor bloated.
The tool surface covers the full intended workflow: research, implementation, review, and an orchestrated research→implement→review→fix loop. There are no obvious dead ends or missing core operations for the stated domain.