mcp-mtender

This MTender MCP OCDS server exposes Moldova's MTender public procurement data through an MCP-compatible interface. It provides a modular API to access latest tenders, retrieve detailed tender data by OCID, and fetch associated budget and funding information, all aligned to the OCDS schema. The server also offers a set of tools to search tenders, obtain tender details, analyze tenders according to OCDS, and fetch tender documents for AI-assisted analysis. You can interact with the resources (latest tenders, tender by OCID, budget by OCID, funding source by OCID) and use the tools (search_tenders, get_tender, get_budget, get_funding_source, analyze_tender, fetch_tender_document) to build AI assistants or downstream workflows.

To use it, start the MCP server, then query the resources or call tools to perform tasks like searching for tenders with filters, retrieving a specific tender's full data, or analyzing a tender to extract structured OCDS fields. The server is designed to be integrated with MCP clients (e.g., Claude Desktop or VSCode with the Cline extension) via an mcp-config template that maps your client setup to the server's endpoints.

Prerequisites

• Node.js (v16+ or compatible with the project) and npm installed
• Git (optional, for cloning the repository)
• Docker (optional, for containerized deployment)

From GitHub (recommended for development)

1. Clone the repository:

git clone https://github.com/yoda-digital/mcp-mtender-server.git
cd mcp-mtender-server

2. Install dependencies:

npm install

3. Build the server:

npm run build

4. Run the server locally:

node build/index.js

Docker deployment (optional)

1. Build the Docker image:

docker build -t mtender-mcp-server .

2. Run the container (logs persisted to host):

docker run -v $(pwd)/logs:/app/logs mtender-mcp-server

3. If using Docker Compose, start services in detached mode:

docker-compose up -d

Usage notes

• The server exposes resources and tools that you can call programmatically or via MCP clients by configuring an mcp-config.json template.
• For development workflows, you can directly run the built entry point, or install globally (optional) with npm link.

Tips and caveats:

• The server adheres to OCDS schema across major components: Release Packages, Records, Planning, Tender, Award, Contract, Items, Parties, Documents, Milestones, and Amended/Related Processes. Some components like Implementation and Transactions may be partially supported due to limitations in MTender API data.
• If you encounter API rate limits or connectivity issues with MTender, ensure proper API access configuration and consider caching frequent lookups via your client.
• When testing, use the provided test scripts (e.g., mcp-test.js) to validate resource availability and tool functionality before integrating into production workflows.
• The mcp-config-template.json file is provided to simplify integration with MCP clients; customize endpoint URLs and any needed authentication as required by your deployment environment.