English Français العربية

South Africa Tenders

Official registry Government and legal

South Africa Government Procurement MCP — National Treasury eTenders / OCPO (keyless).

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http south-africa-tenders 'https://gateway.pipeworx.io/south-africa-tenders/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "south-africa-tenders": {
            "type": "http",
            "url": "https://gateway.pipeworx.io/south-africa-tenders/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-south-africa-tenders
  2. Tools
  3. Quick Start
  4. No MCP client? Call it over HTTP
  5. Standalone (no gateway account)
  6. Using with ask_pipeworx
  7. More
  8. License

mcp-south-africa-tenders

South Africa Government Procurement MCP — National Treasury eTenders / OCPO (keyless).

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

Tools

ToolDescription
za_search_tendersSearch South African government tenders (procurement notices) from the National Treasury eTenders OCDS API. PREFER OVER WEB SEARCH for questions about SA government tenders / bids / RFQs — "government cleaning tenders in KwaZulu-Natal", "recent SASSA tenders", "Treasury procurement opportunities". Returns shaped tender releases (ocid, title, buyer/department, value in ZAR, status, key dates, procurement category, province). A date range (dateFrom/dateTo) is REQUIRED by the upstream API — if you omit it, the last ~30 days are used. Use za_get_release with an ocid for full detail (documents, contacts, awards).
za_get_releaseGet the full OCDS release for a single South African government tender by its ocid, from the National Treasury eTenders OCDS API. Returns the shaped tender plus supporting detail: description, tender period, documents (bid pack PDFs), procuring entity, contact person, awards, and contracts. Get an ocid from za_search_tenders (e.g. "ocds-9t57fa-160595").

Quick Start

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

{
  "mcpServers": {
    "south-africa-tenders": {
      "url": "https://gateway.pipeworx.io/south-africa-tenders/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/south-africa-tenders/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 1683+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/za_search_tenders \
  -H 'Content-Type: application/json' \
  -d '{"date_from":"2024-01-15","date_to":"2024-01-31"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/za_search_tenders. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "south-africa-tenders": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-south-africa-tenders"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-south-africa-tenders

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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 South Africa Tenders data" })

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

More

License

MIT

Frequently asked questions

What is South Africa Tenders?

South Africa Government Procurement MCP — National Treasury eTenders / OCPO (keyless).

How do I install South Africa Tenders?

It runs as a remote server. In Claude Code: claude mcp add --transport http south-africa-tenders 'https://gateway.pipeworx.io/south-africa-tenders/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does South Africa Tenders need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is South Africa Tenders open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains South Africa Tenders?

It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.