freebuff-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREEBUFF_MCP_TOKEN | No | Token used for authenticated HTTP transport when connecting a remote MCP client. Set this to a long random value before running 'serve-http'. |
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 |
|---|---|
| freebuff_statusB | Detect Freebuff and bridge capabilities. |
| list_projectsA | List discovered Freebuff projects. |
| list_threadsC | List Freebuff Desktop threads. |
| get_threadB | Read thread metadata. |
| get_thread_messagesA | Read visible messages for a thread. |
| get_active_workC | Read visible active work. |
| list_project_filesC | List safe project files. |
| read_project_fileC | Read one safe project file. |
| list_modelsA | List models exposed by the installed bridge. |
| send_messageA | Send a text prompt to an existing Freebuff thread. |
| stop_threadB | Stop a running Freebuff turn. |
| resume_threadC | Resume a paused Freebuff thread. |
| set_modelC | Set the model for an existing thread when supported. |
| set_reasoningC | Set the reasoning effort for an existing thread when supported. |
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 14 tools
Each tool targets a distinct resource/action: status, projects, threads, messages, active work, files, models, and thread controls are clearly separated. get_thread vs get_thread_messages and send_message vs resume_thread are differentiated by metadata/content and new-prompt vs resume semantics.
Most tools follow a verb_noun snake_case pattern (list_*, get_*, send_message, set_model), which is predictable. The main outlier is freebuff_status, which lacks a verb, and read_project_file introduces a minor verb variation versus get_*.
At 14 tools, the surface is well-scoped for a Freebuff bridge: discovery/status, project/thread inspection, file access, model listing, messaging, and turn control each have a place. No tool feels redundant or bloated.
The set covers the main inspect-and-interact workflow: list/read threads and files, send messages, stop/resume turns, and configure model/reasoning. Obvious gaps are thread/project creation/deletion and explicit per-thread model/reasoning read-back, though these may be intentionally outside the bridge's scope.