mcp-cnes
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_CNES_BASE_URL | No | Base URL for ElastiCNES. | |
| MCP_CNES_DATA_DIR | No | Directory for downloaded data. | downloads |
| MCP_CNES_MAX_BEDS | No | Maximum number of beds for filtering. | 150 |
| MCP_CNES_MIN_BEDS | No | Minimum number of beds for filtering. | 50 |
| MCP_CNES_MAX_DELAY | No | Maximum delay between requests. | |
| MCP_CNES_MIN_DELAY | No | Minimum delay between requests. | |
| MCP_CNES_COMPETENCE | No | Competence (competência) for CNES data. | 202512 |
| MCP_CNES_KIBANA_API | No | Kibana API endpoint. | |
| MCP_CNES_OUTPUT_DIR | No | Directory for output files. | . |
| MCP_CNES_MAX_RETRIES | No | Maximum number of retries. | |
| MCP_CNES_RETRY_DELAY | No | Delay between retries. | |
| MCP_CNES_DASHBOARD_URL | No | Dashboard URL. | |
| MCP_CNES_TARGET_CITIES | No | JSON object with regions and cities. | |
| MCP_CNES_REQUEST_TIMEOUT | No | Request timeout in seconds. | 60 |
| MCP_CNES_BROWSER_TIMEOUT_MS | No | Browser timeout in milliseconds. | 60000 |
| MCP_CNES_DIRECTOR_CBO_CODES | No | Comma-separated CBO codes for directors. | |
| MCP_CNES_PRIVATE_NATURE_CODES | No | Comma-separated codes for private nature. |
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 |
|---|---|
| cnes_load_dataA | Carrega e consolida atomicamente um CSV exportado do CNES. |
| cnes_search_municipioA | Busca estabelecimentos por município e faixa opcional de leitos. |
| cnes_search_cnesA | Busca um estabelecimento pelo código CNES de sete dígitos. |
| cnes_search_ufB | Busca estabelecimentos por UF e faixa opcional de leitos. |
| cnes_statisticsA | Retorna estatísticas dos dados atualmente carregados. |
| cnes_download_instructionsA | Explica como obter um CSV no dashboard oficial do CNES. |
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 6 tools
Each tool has a clearly distinct purpose: loading data, retrieving instructions, performing three different types of searches (by municipality, CNES code, or UF), and computing statistics. There is no overlap or ambiguity between these operations.
All tools share the 'cnes_' prefix and use lowercase with underscores. Most follow a verb_target pattern (load_data, search_municipio, etc.), though 'cnes_statistics' is a noun rather than a verb, deviating slightly from the pattern.
Six tools is well-suited for a CNES data server covering ingest, guidance, multiple query methods, and statistics. The count feels neither sparse nor bloated, and each tool contributes a necessary function.
The server covers the full workflow: loading data, searching by key identifiers (CNES code, municipality, UF), and generating statistics. Minor gaps exist, such as no explicit way to clear or update loaded data, but the atomic load operation and search coverage handle core needs well.