Boxtalk Data MCP Server
Related Servers
Alternatives to Boxtalk Data MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceA read-only MCP server for browsing and querying SQL Server databases, providing tools to list schemas, tables, describe columns, and execute safe SELECT queries with validated parameters.15-
- AlicenseNot gradedqualityDmaintenanceRead-only SQL Server MCP server enabling safe database queries, table listing, and schema inspection with built-in security protections.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for SQL Server database interactions, providing tools to list databases, get schema, and execute parameterized SELECT queries.10 npm1MIT
- AlicenseAqualityBmaintenanceMCP server for Microsoft SQL Server that lets LLMs explore schema and execute read-only SELECT queries, with optional stored procedure execution when explicitly enabled.348 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables querying SQL Server databases via tools for table search, SELECT execution, and table info retrieval.-
- AlicenseNot gradedqualityAmaintenanceMCP server for safely exposing SQL Server database capabilities to LLM clients, with read-only mode, security features, and observability.28MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_table_count retrieves record counts, get_table_data fetches paginated records, get_table_structure provides schema information, and query_data executes custom SELECT queries. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_table_count, get_table_data, get_table_structure, query_data). The naming is uniform and predictable, with 'get_' prefix for three tools and 'query_' for the fourth, both clearly indicating actions on data resources.
With 4 tools, this server is well-scoped for its purpose of SQL Server data access. Each tool earns its place by covering essential operations: counting, retrieving, inspecting structure, and querying data. The count is neither too sparse nor bloated, fitting the domain appropriately.
The toolset provides strong coverage for read-only data access, including counts, paginated data, schema, and custom queries. However, there are minor gaps, such as no tools for metadata operations (e.g., listing tables or databases) or handling non-SELECT queries, which agents might need to work around for broader database interactions.