remus-mcp
Related Servers
Alternatives to remus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store and retrieve persistent memory through MCP over HTTP (Streamable HTTP and compatible SSE) or stdio.Apache 2.0
- AlicenseAqualityAmaintenanceEnables AI hosts to list database starter templates, create and validate schemas, export SQL DDL and Java JPA entities/repositories, and save or retrieve local project versions through stdio MCP tools.11MIT
- AlicenseNot gradedqualityDmaintenanceA universal SQLite database management tool that enables SQL query execution through MCP protocol. Supports SELECT/INSERT/UPDATE/DELETE/CREATE operations with built-in SQL injection protection across stdio, SSE, and streamable-http communication modes.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to interact with a Mudbase project by listing and querying collections, reading and writing documents, searching across the project, and managing files in storage.1428 npmMIT
- AlicenseCqualityAmaintenanceEnables MCP-compatible agents to operate a versioned shared workspace system through standard tools, including project initialization, file operations, branching, merging, publishing, checkpoints, deduplicated storage, command execution, and background process management over stdio or Streamable HTTP.4153 npmMIT
- AlicenseBqualityCmaintenanceEnables MCP clients to inspect and operate SQLite, PostgreSQL, MySQL/MariaDB, Oracle, SQL Server and MongoDB through 16 tools covering schema discovery, parameterized SQL reads and transactions, MongoDB document operations, and concurrent hybrid SQL/MongoDB queries. Runs locally over stdio or loopback HTTP with pooled connections, bounded concurrency, row and response limits, and read-only defaults.16MIT
TDQS
Scored across 20 tools
Each tool maps to a distinct action on a distinct resource: entities, traces, projects, or files. Even similar tools like get_traces and trace_matrix differ clearly in scope (per-entity vs. matrix-level), and the CRUD operations for entities and traces are unambiguous.
Naming mixes multiple patterns: rem_ prefix for entity operations, trace_ prefix for some trace operations (but get_traces and trace_matrix deviate), project_ prefix for some project tools (but open_project, close_project, list_projects don't follow). Generic verbs like validate_project, export_xml, undo_last break the prefix pattern. While still readable, the inconsistency is noticeable.
With 20 tools, the set is on the heavier side but each tool addresses a specific requirement in a comprehensive project/traceability management system. No redundant or dead-weight tools; the count is justified by the domain's complexity.
The tool surface covers the core lifecycle: project create/open/close/list/clone, entity CRUD, trace management, validation, import/export, history (undo/change log), and rendering. A notable gap is the lack of project deletion or explicit project update, but agents can work around this by cloning and closing projects.