Raccoon MCP
Related Servers
Alternatives to Raccoon MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityFmaintenanceThis MCP server gives an AI coding host controlled, client-agnostic access to a local machine's developer capabilities: transactional file edits, shell and PTY execution, Git and project inspection, language-server operations, isolated browser automation, Windows UI automation, VS Code state, durable jobs, and checkpoints, all bounded by filesystem root allowlisting and resource admission controls. It speaks standard MCP over stdio, Streamable HTTP, and legacy HTTP+SSE, and can also run headless as a long-lived job runner without any hosted model vendor.114ISC
- FlicenseNot gradedqualityCmaintenanceAn AI-powered development assistant that enables LLMs to securely interact with local development tools including Git, filesystem, Docker, PostgreSQL, and GitHub via the Model Context Protocol.-
- FlicenseNot gradedqualityDmaintenanceA secure Model Context Protocol server providing HTTP endpoints for AI agent tool execution, including file system operations, shell commands, and LLM-based code generation.1-
- AlicenseAqualityDmaintenanceA Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.141Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.-
- AlicenseNot gradedqualityDmaintenanceA comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.146 npm2MIT
TDQS
Scored across 105 tools
The toolset contains numerous overlapping tools across process management (start_process vs process_start, list_sessions vs process_list), file operations (fs_read_many vs read_multiple_files, fs_write_text vs write_file), and feedback aliases, making it hard to pick the right tool without deep inspection. While descriptions sometimes differentiate (e.g., recursive vs non-recursive listing), the sheer volume and redundancy cause frequent ambiguity.
Names are mostly snake_case but follow inconsistent patterns: some use domain prefixes (fs_, process_, adb_, dev_pipeline_), while similar operations use bare verb_noun (read_file, write_file) or noun_verb (process_start vs start_process). The mixed conventions, especially duplicate families for the same domain, reduce predictability.
With 105 tools, the surface is far beyond the recommended 3-15 range and even the 25+ threshold for 'too many,' indicating severe over-scoping. The server would be very difficult for an agent to navigate and likely contains many redundant or rarely used tools.
Coverage is broad and deep across file system, process, ADB, desktop, git, build, pipeline, database, and configuration domains, with full lifecycle tools in many areas. Minor gaps exist (e.g., no explicit secret set/delete, limited git operations), but shell_run can often compensate when enabled.