channelshift-mcp
Related Servers
Alternatives to channelshift-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables executing SQL queries, managing databases, and switching between multiple project environments via MCP, without requiring a local MySQL client.143,689 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.25 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 gradedqualityAmaintenanceProvides safe, configurable SQL database access via MCP tools, enabling schema introspection, predefined queries, and structured updates with multi-backend support.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for terminal session control, serial/SSH/Shell connections, workspace configuration, J-Link debugging, RTT logging, and UI interaction, enabling AI hosts to collaboratively operate embedded development workflows.AGPL 3.0
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: listing templates, creating a schema from a template, validating, exporting to SQL or Java, and saving/listing/getting local project versions. The only surface similarity is between list_templates and list_projects, but their descriptions make the distinction explicit. No tools are interchangeable.
All tools use consistent snake_case verb_noun naming: list_templates, create_schema_from_template, validate_schema, export_sql, export_java, save_project, list_projects, get_project. The longer create_schema_from_template still follows the same predictable convention.
Eight tools are well-scoped for a database schema starter/generation server. Each tool covers a distinct stage or operation, and the count is neither thin nor bloated.
The surface covers templates, creation, validation, SQL/Java export, and local project persistence/retrieval. Minor gaps exist, such as no explicit delete_project or get_template operation, and there is no update operation for saved schemas, though the immutable-version design likely makes update/delete intentional omissions.