Protheus Chat MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PGHOST | No | Database host | localhost |
| PGPORT | No | Database port | 5433 |
| PGUSER | Yes | Database user | |
| PGDATABASE | Yes | Database name | |
| PGPASSWORD | Yes | Database password | |
| COHERE_API_KEY | Yes | Cohere API key (reranking) | |
| OPENAI_API_KEY | Yes | OpenAI API key (embeddings) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| protheus_searchC | Search the Protheus FAQ knowledge base for answers about TOTVS Protheus ERP |
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 1 tool
With only one tool, there is no possibility of ambiguity or confusion between different tools.
A single tool enforces perfect naming consistency; there is no pattern to conflict.
One tool is borderline; for a FAQ knowledge base, a search tool alone may be insufficient for full interaction (e.g., retrieving full answers or browsing categories).
The tool covers search but lacks complementary operations like retrieving detailed results or listing topics, leaving notable gaps for a comprehensive FAQ toolset.