tabletalk
Related Servers
Alternatives to tabletalk
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude and other MCP clients to map a SQLite database's schema and run read-only SQL queries against it, with writes blocked at the SQLite level through multiple enforcement layers. Results come back as context-friendly Markdown tables with row caps and a query timeout.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read-only query a SQLite database, inspect schema and table summaries, and execute SELECT queries with pagination through MCP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to inspect a local SQLite database's tables, columns, and schema, and run safe read-only SQL queries with capped JSON results.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and other MCP clients to run read-only, policy-checked SQL queries against SQLite databases, with table and column allowlists, PII restrictions, audit logging, and time and row budgets.MIT
- AlicenseBqualityBmaintenanceEnables AI assistants and MCP clients to safely inspect allow-listed SQLite databases by listing tables, describing schemas, running capped read-only queries, sampling rows, and exporting CSV, with writes blocked unless explicitly enabled.7MIT
- AlicenseAqualityBmaintenanceEnables Claude or any MCP host to explore and query a SQLite database through read-only tools for listing tables, describing schemas, and running SQL queries.3MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: ask_database handles natural language queries, run_sql executes direct SQL, and describe_schema exposes metadata. Even though ask_database and run_sql both query data, their interaction modes are different and descriptions make the boundaries explicit.
All tool names follow a consistent verb_noun pattern in snake_case: ask_database, run_sql, describe_schema. This makes the naming predictable and easy to extend.
Three tools is a compact, well-scoped set for a database query assistant. Each tool serves a necessary role—schema discovery, natural language querying, and direct SQL access—without redundancy or bloat.
For its stated read-only querying purpose, the tool surface is complete: describe_schema enables understanding the data, ask_database handles plain-language questions, and run_sql provides raw querying capability. No obvious dead ends or missing operations exist within this scope.