mcp-kpi-server
Related Servers
Alternatives to mcp-kpi-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with a DuckDB database by executing arbitrary SQL through a single unified query tool, supporting operations such as querying, table creation, and schema inspection. Supports a read-only mode that enforces DuckDB's native protection to prevent any writes.-
- AlicenseAqualityCmaintenanceEnables AI agents to discover and execute analytical queries on a DuckDB dataset through typed MCP tools, with guarded read-only SQL support for complex calculations without direct database access.6MIT
- AlicenseAqualityAmaintenanceEnables AI agents to inspect database schemas and run strictly read-only SQL queries with guardrails against destructive statements, multi-statement chaining, and unbounded scans. Supports SQLite natively and PostgreSQL optionally.4MIT
- AlicenseAqualityBmaintenanceEnables AI agents and developers to introspect SQLite schemas, run sandboxed read-only queries with pagination, inspect query plans, and generate token-dense database summaries for LLM context. All operations enforce multi-layer read-only safety so databases can be explored without risk of mutation.5MIT
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with a local DuckDB database through a single unified SQL query tool, supporting operations such as querying, table creation, joins, and schema inspection. Optional read-only mode enforces native write protection so data can be analyzed safely without unintended changes.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients and LLMs to interact with a DuckDB database through SQL query execution, table creation, and schema inspection, with optional read-only operation.-
TDQS
Scored across 4 tools
Each tool occupies a clearly distinct role: listing tables, describing a table, running an arbitrary read-only query, and fetching a named KPI. The only potential overlap is get_kpi vs run_select, but the descriptions make it clear one is a curated convenience wrapper and the other is generic SQL.
All four tools follow a consistent snake_case verb_noun pattern (list_tables, describe_table, run_select, get_kpi). Verb choice matches the action type well (list vs describe vs run vs get).
Four tools is proportionate to a narrow read-only KPI/query server; each tool covers a distinct stage of the workflow (discover schema, inspect schema, ad-hoc query, curated KPI). Nothing feels redundant or missing at the count level.
The surface covers schema discovery, inspection, ad-hoc reads, and predefined KPIs, which is solid for a read-only server. Minor gaps: no tool to enumerate available KPI names (agents must parse descriptions) and the 200-row cap has no pagination or export path, which could dead-end on larger results.