channelshift-mcp
Related Servers
Alternatives to channelshift-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseCqualityCmaintenanceEnables executing SQL queries, managing databases, and switching between multiple project environments via MCP, without requiring a local MySQL client.14458 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables remote database access (RDBMS and MongoDB) through MCP tools, supporting read/write queries, schema management, and more.-
- AlicenseNot gradedqualityCmaintenanceExposes sqlite3 database functionality as MCP tools, enabling SQL query execution, schema management, and CRUD operations.29 PyPI1MIT
- AlicenseCqualityBmaintenanceEnables interaction with REMUS Jet databases through the MCP protocol, supporting local stdio and remote HTTP/SSE transports for database operations and project management.20AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage collections and records, handle user authentication and account operations, and create database backups through MCP tools. Supports schema creation, CRUD operations, pagination, filtering, and relationship expansion.10 npmISC
TDQS
Scored across 11 tools
Each tool targets a clearly distinct resource or action: requirements review, reference collection, schema creation from templates, project save/get/list, template listing, validation, Java/SQL export, and platform status. Even the two platform-connected tools (review_requirements and collect_reference) have distinct objects and purposes, so misselection is unlikely.
Names are consistently snake_case and mostly follow a verb_noun pattern (review_requirements, collect_reference, create_schema_from_template, export_java, export_sql, get_project, list_projects, list_templates, save_project, validate_schema). service_status is a minor deviation as a noun_noun phrase rather than verb_noun.
11 tools is well within the ideal range for a scoped server combining schema project management with auxiliary platform operations. Each tool has a clear purpose and no redundant operations are apparent.
Core schema lifecycle is covered: create from template, save immutable versions, get by version ID, list projects/templates, validate, and export to Java and SQL. Some gaps remain, such as delete/update for saved projects and richer requirement/reference lifecycle beyond one-shot review and collection, though immutability partially justifies missing update.