mcp-crewai-giulia-ai
Related Servers
Alternatives to mcp-crewai-giulia-ai
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn MCP server that gives AI agents direct read-only access to PostgreSQL databases, enabling natural language analytics through tools for schema exploration, querying, trend analysis, and data quality checks.115MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that exposes PostgreSQL/MySQL/SQLite/MongoDB databases to AI agents, converting natural language questions into SQL queries with configurable LLM providers and safe read-only operations.-
- AlicenseNot gradedqualityCmaintenanceRead-only Text-to-SQL MCP server for PostgreSQL and MySQL that lets users query databases using natural language, with robust multi-layer safety guarantees against writes.20 npmMIT
- AlicenseAqualityDmaintenanceA production-grade MCP server that gives AI agents safe, authenticated access to a PostgreSQL database.3MIT
- FlicenseAqualityBmaintenanceA security-hardened Postgres MCP server that enables LLM agents to run safe, read-only SQL queries with enforcement via SQL-AST inspection and read-only transactions.1-
- FlicenseNot gradedqualityAmaintenanceAn MCP server that exposes relational databases (PostgreSQL/MySQL) to AI agents with natural language to SQL query support.19-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one discovers available databases, the other answers natural-language questions via SQL. The cross-references in each description make the intended order of use explicit, leaving no realistic chance of misselection.
Both names follow a verb_noun snake_case pattern in Portuguese (buscar_dados_sql, listar_databases), which is readable and predictable. The minor deviation is the '_sql' suffix on one tool that isn't mirrored in the other.
Two tools is borderline thin for a server, though for a strictly read-only NL-to-SQL workflow it is defensible. A schema-inspection or query-explanation tool would round out the set without bloat.
Discovery plus read-only querying covers the core stated purpose with no obvious dead ends. A dedicated schema/table introspection tool is a minor gap, since schema knowledge is currently only implicit inside buscar_dados_sql.