mcp -arch-dotnet

This MCP server is a .NET 8.0-based implementation of the Model Context Protocol (MCP) built around a Clean Architecture structure. It exposes a REST API via ASP.NET Core with endpoints to process MCP requests, manage resources, and perform JSON-RPC 2.0 file system operations. Once running, you can interact with the API through the Swagger UI or directly with HTTP clients. The API includes standard MCP endpoints for processing requests and messages, as well as a dedicated FileServer MCP that supports JSON-RPC 2.0 methods for listing, reading, writing, and managing files and directories. Start the server, browse the Swagger UI to discover the available endpoints, and use the provided endpoints to integrate with your models, resource providers, or external services.

Prerequisites:

• .NET 8.0 SDK or later (for building locally) or a docker-enabled environment
• Docker installed and running (for the recommended containerized setup)
• PowerShell or Bash for running setup commands (optional)

Option A: Run with Docker (recommended)

1. Ensure Docker is running on your machine.
2. Pull and run the image corresponding to the MCP Architecture .NET server: docker run -d --name floradu88-mcp-server-arch-dotnet -p 5000:5000 -p 5001:5001 floradu88/mcp-architecture-dotnet:latest
3. Access the API at http://localhost:5000 or https://localhost:5001 (Swagger at https://localhost:5001/swagger).

Option B: Build and run locally (if you have the source)

1. Clone the repository or obtain the project source.
2. Open the solution in Visual Studio 2022+ and set McpArchitecture.Api as the startup project, then run.
3. Alternatively, from the command line: cd McpArchitecture.Api dotnet restore dotnet run Access the API at http://localhost:5000 (or the configured URL).

Prerequisites in short:

• Docker for containerized runs or .NET 8 SDK for local builds
• IDE (Visual Studio 2022+) or CLI tools (dotnet)
• A configured environment (e.g., appsettings.json) for MCP base URL, timeouts, and logging if running locally

Tips and considerations:

• The API exposes endpoints for MCP operations and a JSON-RPC 2.0 FileServer suite; test with Swagger or a client.
• Ensure TLS is configured if exposing HTTPS in production; adjust ASPNETCORE_URLS or docker port mappings as needed.
• The project follows Clean Architecture, so adding new use cases typically involves extending the Application layer and related interfaces while preserving boundaries.
• If you modify configuration, update appsettings.json accordingly (MCP base URL, timeouts, logging levels).
• Common issues often involve missing NuGet packages, incorrect project references, or port binding conflicts; verify container ports and project references when troubleshooting.