crew-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREW_SCOUT | No | Quick override for the scout role worker chain (e.g., 'local,chatgpt'). | |
| CREW_NUM_CTX | No | Quick override for the number of context tokens (e.g., 16384). | |
| CREW_REVIEWER | No | Quick override for the reviewer role worker chain (e.g., 'chatgpt'). | |
| CREW_WORKSPACE | No | Set the workspace directory for the server to use instead of the launch directory. | |
| CREW_OLLAMA_URL | No | Quick override for the Ollama server URL (e.g., http://localhost:11434). | |
| CREW_OLLAMA_MODEL | No | Quick override for the Ollama model to use (e.g., a model name). |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crew_statusA | Show crew configuration, the workspace it will read, and which workers (local GPU, ChatGPT, API) are available. Run this first if another crew tool errors. |
| crew_reconA | Send a scout (local GPU first, ChatGPT as fallback) to map the code relevant to a question: files, functions, coverage of each stage, and evidence-backed risks. Use it before reading lots of files yourself, to save your context. Results are leads to confirm, not proof. |
| crew_review_diffA | Have a scout review the current working-tree changes (staged, unstaged and new files) for bugs, security, concurrency and data-integrity problems. Findings are split into evidence-checked (the quoted code really exists) and unverified. Run it after making changes and before saying you're done. |
| crew_second_opinionA | Ask an independent reviewer (ChatGPT by default) to critique a plan, a design, or the current diff. Use it for risky work: payments, auth, migrations, concurrency. Expect disagreement; weigh it, don't just accept it. |
| crew_check_citationsA | Deterministically check file:line references in a piece of text against the repository: the file exists, the lines exist, and a backticked identifier on the same line really appears near those lines. No model involved. Use it on your own analysis before presenting it. |
| crew_statsA | Show what the crew did: per worker, calls, time, files and characters read, tokens generated, and findings quote-checked vs unverified. ChatGPT calls show calls and time only. Includes a clearly labeled ESTIMATE of context kept out of Claude. Read from a local metadata-only log (no prompts or code). |
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
Most tools target clearly distinct actions: status/config, stats/metrics, citation-checking, code recon, second-opinion critique, and diff review. The main overlap is between crew_second_opinion and crew_review_diff, since both critique a diff, though descriptions separate a general design/plan critique from a bug/security-focused diff review.
All tools share the crew_ prefix and mostly follow a verb_noun pattern (check_citations, review_diff, second_opinion). A few are bare nouns (stats, status, recon), which is a minor deviation but still readable and predictable.
Six tools is well-scoped for a crew/delegation server. Each tool earns its place across setup, observability, exploration, verification, and review, with no redundancy padding the count.
The surface covers the full review workflow: status, stats, recon, second opinion, citation verification, and diff review, giving no obvious dead ends. Configuration is read-only (status) with no way to set up crew/workspace, a minor gap users can work around.