Japan Procurement MCP server

@pipeworx/japan-procurement

Japanese government tender notices — bid announcements from national ministries, all 47 prefectures and municipalities, sourced from the 官公需情報ポータルサイト (Kankōju public procurement portal) run by the Japan Small and Medium Enterprise Agency.

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

Tools

body. Accepts Japanese or ASCII and the portal's operators (AND / OR / ANDNOT / NOT, parentheses). Filters: category, prefecture, procedure type, organisation, notice title, announcement-date range.

• japantenderssearch(query, …) — keyword search across every publishing

with no keyword. Takes "Tokyo", "東京都" or "13", comma-separated for several.

• japantendersby_prefecture(prefecture, …) — browse a prefecture's notices

buyer published ("国土交通省", "横浜市"), partial match.

• japantendersbyorganization(organizationname, …) — everything a named

47 JIS X0401 prefecture codes. Call it when a filter value is rejected.

• japantenderreference() — the accepted categories, procedure types and all

Every notice carries the buyer, title, announcement date, the original notice URL, attachment links, and — where the publisher supplied them — the bid submission date, opening date, delivery deadline, performance location and required bidder certification.

Auth

Keyless.

Data sources

Spec: (V1.1, 2016-05-27).

• — the portal's documented search API, XML.

Things the next person would otherwise rediscover the hard way:

SearchHits=0 — a clean 200 that reads as "Hokkaido publishes no tenders". LG_Code=01 returns ~50k. The pack pads for you; don't undo that.

• LGCode must be zero-padded to two digits. LGCode=1 returns

Japanese label returns internal error: query error: syntax error. Same for Procedure_Type (1–3). The pack maps names and labels to codes and rejects anything unmappable with the valid set named, rather than forwarding it.

• Category must be the numeric code (1 物品 / 2 工事 / 3 役務). Passing the

(values above that are silently treated as 1,000). To walk a larger result set, narrow with CFTIssueDate — the pack surfaces this as paging in the response whenever total_hits exceeds what it returned.

• No offset or page parameter exists. Count caps at 1,000 per call

is required**; with none the API answers no searchword. That is why the browse tools require a prefecture or an organisation.

• At least one of Query / ProjectName / OrganizationName / LGCode

thousands of characters (it is the OCR/extract of the linked PDF, and can include the whole unit-price schedule). The pack returns a 600-character preview with descriptiontruncated, and up to 20,000 characters under fulltext: true.

• ProjectDescription is the full extracted notice text, routinely tens of

them — TenderSubmissionDeadline, OpeningTendersEvent, Location, Certification and ItemCode are frequently absent, especially on municipal notices.

• Optional fields are omitted, not emptied, when the publisher did not supply

Quick Start

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

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

What this endpoint actually serves

Shortened. The full README is on GitHub.