freebuff-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEBUFF_API_KEY | No | Alternative environment variable for the API key; same as FREEBUFF_API_KEY. | |
| FREEBUFF_API_KEY | No | API key for Freebuff/Codebuff. Can also be supplied via --api-key argument or CODEBUFF_API_KEY environment variable. | |
| FREEBUFF_MCP_DIR | No | Directory for session persistence. Defaults to ~/.freebuff-mcp/sessions. | |
| FREEBUFF_MCP_MAX_AGE_DAYS | No | Maximum age in days for sessions before pruning. | 30 |
| FREEBUFF_MCP_MAX_SESSIONS | No | Maximum number of sessions to keep when pruning. | 50 |
| FREEBUFF_MCP_RESUME_MAX_TOKENS | No | Token estimate above which resuming is refused unless force_resume is true. | 150000 |
| FREEBUFF_MCP_RESUME_WARN_TOKENS | No | Token estimate above which resuming prints a warning. | 80000 |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| freebuff_runA | Run the Freebuff coding agent on a prompt, inside a workspace folder. By default runs the built-in read-only 'freebuff-ask' agent, which can read files, search code, and answer questions but cannot modify anything — safe for codebase Q&A. Pass agent: 'codebuff/base@0.0.16' to let the agent edit files and run commands. Returns the agent's final answer plus a log of what it did. Continue a conversation by passing the session_id returned from a previous run (sessions persist across server restarts). |
| freebuff_statusA | Check whether the Freebuff MCP server has valid credentials and can reach the agent backend. |
| freebuff_deleteA | Delete a Freebuff agent session by id — from memory and disk. Returns error if the id is unknown. The transcript resource for a deleted session disappears; active runs must be cancelled (freebuff_stop) before deleting their session. |
| freebuff_stopA | Cancel the currently running Freebuff agent session, if any. |
| freebuff_sessionsA | List Freebuff agent sessions known to this server (memory + persisted on disk). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| sessions-index | JSON index of all Freebuff agent sessions (persisted + in-memory). |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: run executes the agent, stop cancels a run, status checks connectivity, sessions lists stored sessions, and delete removes a session. There is no meaningful overlap or ambiguity between them.
All tools use the freebuff_ prefix and snake_case, and most are verb-based (run, stop, delete, status). The exception is freebuff_sessions, which is a noun rather than an action verb, but it is still predictable and easily understood.
Five tools is well-scoped for the server's purpose: managing and interacting with Freebuff coding agent sessions. Each tool covers a necessary part of the lifecycle without redundancy or bloat.
The tool surface covers the full session lifecycle: create/continue with run, cancel with stop, list with sessions, delete with delete, and validate availability with status. There are no obvious dead ends for the stated domain.