mcpField
B
BrasilAPI MCP Server

BrasilAPI MCP Server

Local
smithery.aiDeveloper Tools7Updated 84w ago
RepositoryVisit website

About BrasilAPI MCP Server

BrasilAPI MCP Server exposes BrasilAPI endpoints to AI applications and agents. It covers Brazilian data such as postal codes, banks, holidays, and taxes through a unified set of tools.

Key features

  1. 01Query postal code and area code data
  2. 02Retrieve bank and holiday information
  3. 03Access tax and other BrasilAPI endpoints
  4. 04Inspect tools and parameters with Smithery

Use cases

  1. 01Look up a Brazilian postal code
  2. 02Check area codes or bank details
  3. 03Retrieve holiday or tax information

MCP support

It provides MCP tools for querying every endpoint available through BrasilAPI, allowing MCP clients to access Brazilian data.

#mcp#llm#mcp-server

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "brasil-api": {
      "command": "npx",
      "args": [
        "-y",
        "@smithery/cli"
      ]
    }
  }
}
Run commandnpx -y @smithery/cli

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@smithery/cli

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

BrasilAPI MCP Server

smithery badge

Query a variety of data from Brasil resources seamlessly. Access information on postal codes, area codes, banks, holidays, taxes, and more through a unified interface. Enhance your AI agents and applications with rich and updated data from BrasilAPI effortlessly.

Check the complete and official documentation from BrasilAPI here.

Tools

This server provides tools to query every endpoint available from BrasilAPI. Under the hood, it uses this JS client to communicate with the API: https://github.com/WillianAgostini/brasilapi-js

Check the Tools page in Smithery to inspect and test each one of them.

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch
Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:

npm run inspector

To generate an updated build and inspect:

npm run build-and-inspect

The Inspector will provide a URL to access debugging tools in your browser.

Integration with AI applications

Running through Smithery

Run the server automatically via Smithery:

npx -y @smithery/cli install @mauricio-cantu/brasil-api-mcp-server
Usage with Claude
npx -y @smithery/cli@latest install @mauricio-cantu/brasil-api-mcp-server --client claude
Cursor and other integrations

Check the Server page in Smithery to get other integration options such as Cursor and more.

Running the server with a local copy

After you've downloaded this project, you can run the server using node:

node /absolute/path/to/brasil-api-mcp-server/build/index.js

At the root of the project there's also a Dockerfile to build and run the image if you'd like.

Server's capabilities inspection

You can inspect this MCP server's capabilities using Smithery:

npx -y @smithery/cli@latest inspect @mauricio-cantu/brasil-api-mcp-server

This will show you all available tools, their parameters, and how to use them.

Project structure

src/
  ├── apiClient/   # BrasilAPI client
  ├── tools/       # Tools implementations
  ├── types/       # Interfaces and types
  ├── utils/       # Utility functions
  └── index.ts     # MCP main file (server setup and tools listing)

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.