bluebonnet-sales
Related Servers
Alternatives to bluebonnet-sales
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude to answer business questions against a company's retail database — sales summaries, top customers, inventory alerts, customer profiles, and plain-English queries — through read-only SQL tools plus a schema resource and reporting prompt. Access is governed by OAuth 2.1 roles and scopes, column-level PII masking, a SQL guard, rate limits, and audit logging.5MIT
- AlicenseAqualityCmaintenanceEnables Claude to answer questions about a small business's own data by providing predefined sales, customer, refund, and inventory tools, plus a guarded read-only SQL query tool with audit logging.6MIT
- AlicenseAqualityBmaintenanceEnables Claude to run validated, read-only SELECT queries against PostgreSQL while refusing non-approved tables and unsafe statements, capping returned rows, and recording every call in a JSONL audit log.3MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to query and safely write to a Postgres database, driven entirely by one policy file with read-only access by default, column-precise PII masking, and an append-only audit log. SQL is parsed and validated before execution, writes use parameterized queries with dry-run/confirm and transactions, and every call is rate-limited and audited so destructive or exfiltrating requests are refused.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude or any MCP-capable assistant to explore and query a small business's sales, payments, invoices, and expenses through read-only SQL tools, while personal-data columns and write operations are refused by the database policy.MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude to translate natural-language business questions into safe, read-only SQL queries by exposing tools for listing tables, inspecting schemas, and executing row-capped SELECT statements against PostgreSQL.MIT
TDQS
Scored across 7 tools
The schema tools (list_tables, describe_table, run_query) and the canned reports (sales_summary, top_customers, low_stock) each target a clearly different question, and update_order_status is the only mutating tool. The one soft overlap is that run_query could reproduce any of the report tools, so an agent must decide between a prebuilt report and ad-hoc SQL, but the descriptions make the intended choice reasonably clear.
All names are consistently snake_case and readable. The verb_noun pattern holds for list_tables, describe_table, run_query and update_order_status, but the three report tools (sales_summary, top_customers, low_stock) drop the verb and use noun phrases, a minor deviation from an otherwise predictable convention.
Seven tools is well-scoped for a sales-database server: three discovery/query primitives, three focused reports, and one guarded write. Nothing feels redundant or padded, and there is no obvious missing operation forcing extra tools.
The surface covers schema discovery, arbitrary read queries, common sales analytics, inventory alerts, and a confirmed order-status update. There is no detail-level order/customer lookup or any create/delete path, but run_query serves as an escape hatch for read gaps, so the omissions are workaround-able rather than dead ends.