freebuff-mcp
Related Servers
Alternatives to freebuff-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables authorized remote MCP clients to securely reach local Mac or Windows tools over OAuth, including shell commands, file read/write, background jobs, screenshots, UI control, and clipboard access. It can also expose configured Desktop MCP servers and optional Claude Code task delegation.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as ChatGPT and MCP Inspector to securely read and manage files within explicitly allowed local directories over MCP Streamable HTTP, with OAuth support and enforced filesystem restrictions.MIT
- AlicenseCqualityCmaintenanceEnables local MCP clients to securely use the court's digital systems—public process lookup, fee calculation, CNJ metadata queries, and the CAP1G chat—without exposing credentials to the MCP protocol.351MIT
- AlicenseAqualityCmaintenanceProvides desktop AI clients with sandboxed, controlled read, write, search, and management access to user-selected local folders and projects over the Model Context Protocol.212MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to securely access explicitly authorized local project files and run approved development commands with bounded execution and audit logging.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding clients to securely connect to local workspaces through a public MCP endpoint, providing sandboxed file read, write, edit, and terminal command execution within a restricted project directory.1,832 npm1MIT
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.