mcp-brazil-pncp

Brazil PNCP MCP — Brazilian government procurement (keyless).

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool Description

brazil_search_contracts Search signed Brazilian government contracts (contratos) from the official PNCP portal (Portal Nacional de Contratações Públicas). Covers federal, state, and municipal agencies under Lei 14.133/2021. Returns each contract with its PNCP control id, object (Portuguese), global value in BRL, supplier name and tax id (CNPJ/CPF), contracting agency, state/municipality, and signing/validity dates. Dates are YYYYMMDD and filter by PNCP publication date; omit them to get roughly the last 30 days.

brazil_search_tenders Search published Brazilian government tenders / bidding notices (contratações / editais) from the official PNCP portal (Portal Nacional de Contratações Públicas). These are open or recently published procurement opportunities under Lei 14.133/2021. Returns each tender with its PNCP control id, object (Portuguese), estimated value in BRL, procurement modality, agency, state/municipality, proposal open/close dates, and a link to the source system. Dates are YYYYMMDD filtering by PNCP publication date; omit for roughly the last 30 days. The modality defaults to 6 (Pregão Eletrônico), the most common; pass another code to filter differently.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "brazil-pncp": {
      "url": "https://gateway.pipeworx.io/brazil-pncp/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/brazil-pncp/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Brazil Pncp data" })

The gateway picks the right tool and fills the arguments automatically.

License

MIT

Brazil Pncp