SassyMCP
OfficialRelated Servers
Alternatives to SassyMCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA lightweight Windows-native MCP server providing a consolidated suite of 14 tools for shell execution, file operations, and interactive process management. It optimizes efficiency through batch file operations and smart process handling to minimize context window overhead.2 npm4MIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server offers 72 typed tools for Kali Linux pentesting, including recon, web, AD, cracking, C2, remote desktop, and tunneling. It provides structured JSON output, persistent session state, and auto-populated findings for streamlined workflows.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets you execute commands, manage files, run persistent shell sessions, transfer large files, and control background processes on remote machines via a lightweight HTTP agent, useful when SSH/WinRM/SMB are unavailable.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA feature-rich Model Context Protocol server built with FastMCP that provides various tools including basic utilities, network services, file operations, encryption tools, and system information functions.1-
- FlicenseNot gradedqualityDmaintenanceA production-ready, modular MCP server with 40+ tools across 8 categories, featuring dynamic auto-loading and sandboxed security for file system, database, and network operations.-
- FlicenseNot gradedqualityDmaintenanceA powerful filesystem MCP server for AI agents with extensive system access, including filesystem operations, shell execution, Windows tools, reverse engineering, code intelligence, and agent orchestration.1-
TDQS
Scored across 101 tools
The descriptions are unusually diligent about pointing at the right sibling tool (e.g. audit_log vs audit_search vs recent_tool_calls, tool_catalog vs tool_groups vs context_estimate), which rescues many near-neighbors. But with 101 tools there are still numerous overlapping clusters — four audit readers, three usage/introspection stats tools, six persona document tools, five memory query tools, and parallel 'ghq' vs 'gh' GitHub families — so an agent must read cross-references carefully to avoid misselection.
Nearly everything is snake_case under a uniform sassy_ prefix with a predictable group/module segment (memory_, audit_, session_, setup_, update_, persona_, tool_, observability_). Minor deviations exist: bare noun names like sassy_permission, sassy_panel, sassy_batch, sassy_hotkey, sassy_toast, and the get_/set_ pair (get_config/set_config) sit beside verb-first names, but the scheme remains readable and largely mechanical.
101 registered tools is far beyond what a coherent tool surface should expose in one session; the server itself ships sassy_context_estimate, pruning suggestions, and group toggles as damage control for its own size. Even accounting for intentional lazy-loaded groups, the presented surface is an extreme over-extension of scope for any single MCP server.
Coverage is broad and lifecycle-complete for most areas: file read/write/edit/copy/move/safe-delete/diff/archive, shell plus persistent sessions, config get/set, memory and state CRUD, audit reading, setup/update flows, GitHub file/issue/PR paths, and desktop control. Gaps remain — no true unlink (deletion is staged, by design), and several referenced tools (screen_glance/watch/capture, phone_*, crosslink_*, gh_* full family) are absent from the live list, leaving some dead-end pointers that assume dormant groups.