mcp-crewai-giulia-ai
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PG_HOST | Yes | PostgreSQL host. | localhost |
| PG_PORT | No | PostgreSQL port. | 5432 |
| PG_USER | Yes | PostgreSQL user. | |
| LLM_MODEL | Yes | The LLM model to use for SQL generation (e.g., gpt-4o, claude-3-5-sonnet, gemini-1.5-pro, or an OpenRouter model identifier). | |
| PG_PASSWORD | Yes | PostgreSQL password. | |
| GEMINI_API_KEY | No | Google Gemini API key (required if LLM_MODEL is a Gemini model). | |
| OPENAI_API_KEY | No | OpenAI API key (required if LLM_MODEL is an OpenAI model). | |
| ANTHROPIC_API_KEY | No | Anthropic API key (required if LLM_MODEL is an Anthropic model). | |
| OPENROUTER_API_KEY | No | OpenRouter API key (required if LLM_MODEL is an OpenRouter model). | |
| PG_STATEMENT_TIMEOUT_MS | No | Timeout for SQL statements in milliseconds. | 15000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buscar_dados_sqlA | Responde uma pergunta em linguagem natural consultando o banco indicado. O SQL é gerado a partir do schema, validado como somente-leitura e executado numa
sessão read-only. Use |
| listar_databasesA | Lista os bancos disponíveis para consulta. Use antes de |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.