brasilapi-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HTTP_PORT | No | Port to listen on when MCP_TRANSPORT is set to 'streamable-http'. Defaults to 8001. | 8001 |
| MCP_TRANSPORT | No | Transport mode for the MCP server. Use 'streamable-http' to run as an HTTP service; if unset, defaults to stdio. | stdio |
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 |
|---|---|
| lookup_cnpjA | Look up a Brazilian company (CNPJ) — legal name, address, status, and business activity. Args: cnpj: CNPJ number, with or without formatting (e.g. "19131243000197" or "19.131.243/0001-97"). |
| lookup_cepA | Look up a Brazilian postal code (CEP) — street, neighborhood, city, state, and coordinates. Args: cep: CEP number, with or without formatting (e.g. "01310930" or "01310-930"). |
| list_banksA | List all Brazilian banks registered with the Central Bank, with their codes (COMPE/ISPB). |
| get_holidaysA | List Brazilian national holidays for a given year. Args: year: Four-digit year (e.g. 2026). |
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 4 tools
Each tool targets a completely distinct resource: companies (CNPJ), postal codes (CEP), banks, and holidays. There is no overlap in purpose or potential for misselection.
Naming is readable and noun-focused, but verbs are inconsistent: 'lookup_' for two tools, then 'list_', and 'get_'. The pattern is not uniform, though the differences are minor and contextually acceptable.
Four tools is slightly thin for a general Brazil data API but reasonable for a focused utility server. Each tool covers a meaningful public data lookup without redundancy.
The server covers a few common lookups but lacks many obvious BrasilAPI endpoints such as CPF (individual taxpayer), state/IBGE data, FIPE vehicle pricing, or DDD area codes. Agents needing these will hit dead ends.