A
licenseC
qualityB
maintenanceEnables interaction with REMUS Jet databases through the MCP protocol, supporting local stdio and remote HTTP/SSE transports for database operations and project management.
20
AGPL 3.0
mudbase-mcp-server
by themudhaxk
Related Servers
Alternatives to mudbase-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides secure, permission-controlled access to Firebase Firestore databases with full CRUD operations, advanced queries, batch operations, and transactions through a standardized MCP interface.2312MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to search and query a team knowledge graph, retrieve document context, upload files for indexing, explore entities and connections, and monitor workspace usage and server health.MIT
- AlicenseNot gradedqualityCmaintenanceProvides authenticated Streamable HTTP MCP access to a MedEval medical-device regulatory workspace, enabling project selection, evidence retrieval, section context, document revision management, and generation/evaluation task control.MIT
- AlicenseNot gradedqualityAmaintenanceEnables local MCP clients to interact with an AuroraCloud workspace, supporting object listing, content reading, search, and task management through authenticated API calls.174Apache 2.0
- AlicenseBqualityDmaintenanceEnables MCP clients to manage Overleaf projects via Git sync, including listing, reading, writing, and syncing files.454MIT
TDQS
A3.9/5.0
Scored across 14 tools
Disambiguation5/5
Each tool targets a distinct resource-action pairing: documents, collections, buckets, and files are cleanly separated. Even similar tools like list_documents and search_documents are distinguished by structured filtering versus full-text search.
Naming Consistency5/5
All tools follow a consistent mudbase_<verb>_<noun> pattern in snake_case, making the API predictable. The only compound name, get_file_download_url, still follows the same get_<resource>_<aspect> convention.
Tool Count5/5
14 tools is well within the ideal range and each tool covers a distinct operation across two coherent domains: document CRUD/search and file storage. No tool feels redundant or unnecessary.
Completeness4/5
Document CRUD, listing, filtering, and search are covered, along with file upload/list/get/delete and signed download URLs. Minor gaps exist around collection lifecycle management and file metadata updates, but agents can accomplish the core workflows without dead ends.
Maintenance
ActivityMaintained
ResponsivenessNo issues