ViaCEP Brasil MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| buscar_endereco_por_cepA | Consulta informações completas de um endereço brasileiro a partir do CEP (Código de Endereçamento Postal). Retorna logradouro, bairro, cidade, estado, região, DDD, IBGE, GIA e SIAFI. O CEP pode ser informado com ou sem hífen (ex: 01001-000 ou 01001000). |
| buscar_cep_por_enderecoA | Pesquisa CEPs brasileiros a partir de informações de endereço: UF (sigla do estado), cidade e logradouro (nome da rua/avenida/etc). Retorna até 50 CEPs correspondentes, ordenados pela proximidade do nome do logradouro. Útil quando o CEP não é conhecido mas o endereço sim. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| readme | Documentação completa do ViaCEP Brasil MCP Server: ferramentas disponíveis, instalação, configuração em clientes MCP (VS Code, Claude, Cursor), exemplos de uso e referência da API ViaCEP. |
TDQS
Scored across 2 tools
The two tools are inverse operations: one fetches an address from a CEP, the other fetches CEPs from an address. Their purposes are clearly distinct and complementary, leaving no ambiguity.
Both tool names follow the same Portuguese pattern 'buscar_X_por_Y' (buscar_endereco_por_cep and buscar_cep_por_endereco), making the naming perfectly consistent and predictable.
With only 2 tools, the count is borderline but appropriate for the narrow domain of CEP lookup. Each tool covers one direction of the search, so no tool feels superfluous.
The server covers the two core operations of the ViaCEP service: address-by-CEP and CEP-by-address. This fully addresses the domain's primary use cases, with no obvious gaps.