MCPP.Net

MCPP.Net is a .NET 8-based MCP server that dynamically converts OpenAPI/Swagger definitions into MCP-compatible tools. Once a Swagger/OpenAPI document is imported, the server automatically generates MCP tool methods for the API endpoints, registers them with the MCP server, and exposes a Swagger UI for testing and discovery. You can import new APIs at any time without restarting the service, manage existing tools (view or delete), and connect MCP clients via SSE to exchange messages using the MCP protocol. This makes external REST services accessible to AI tools through a unified MCP interface.

To use the system, first import a Swagger definition using the provided API endpoint. The server will download, parse, and generate the corresponding MCP tool class, then register it so MCP clients can invoke the API endpoints. You can test the generated tools through the Swagger UI or by sending MCP messages to the server’s endpoints. The server exposes an Import API for adding tools, a tool management API for listing and deleting tools, and an SSE/Message channel for MCP clients to communicate with the tools.

Prerequisites:

• Docker (for containerized deployment) or .NET 8 SDK if running directly
• Internet access to fetch Swagger/OpenAPI definitions
• Basic familiarity with Swagger/OpenAPI and MCP concepts

Option A: Run with Docker

1. Ensure Docker is installed and running.
2. Pull/build the image (adjust image name as needed): docker pull mcppnet:latest docker run -i -p 7103:7103 --name mcppnet mcppnet:latest
3. The server will start and listen on http://localhost:7103 (adjust ports if needed).

Option B: Run with Docker Compose (example)

1. Create docker-compose.yml: version: '3.8' services: mcppnet: image: mcppnet:latest ports: - '7103:7103' environment: - ASPNETCORE_URLS=http://+:7103 restart: unless-stopped
2. Run: docker-compose up -d

Option C: Run directly with .NET (if you prefer native execution)

1. Prerequisite: .NET 8 SDK installed.
2. Clone the repository and navigate to the project: git clone https://github.com/yourusername/MCPP.Net.git cd MCPP.Net
3. Build and run: dotnet build src/MCPP.Net dotnet run --project src/MCPP.Net
4. Access Swagger UI at: https://localhost:7103/swagger/index.html

Tips and common considerations:

• If you plan to expose the MCP server publicly, configure ASPNETCORE_URLS or use a reverse proxy (NGINX/Traefik) and enable TLS.
• The Import API accepts a Swagger URL or local file via POST to /api/Import/Import; ensure CORS or client access is configured as needed.
• Imported tools are stored under ImportedTools and can be listed via GET /api/Import/GetImportedTools; delete with DELETE /api/Import/DeleteImportedTool?nameSpace=YourNamespace&className=YourClass.
• Swagger UI (https://localhost:7103/swagger/index.html) helps validate endpoints and test calls before integrating with MCP clients.
• For MCP client integration, connect via SSE at /sse and send messages to /message as per MCP protocol.
• Environment variables such as ASPNETCORE_URLS, ASPNETCORE_ENVIRONMENT, and logging settings can be adjusted to fit deployment needs.