ceciliasharp/MCPDemo.McpServer_NIC

MCPDemo.McpServer

This is the example code used in the demo of the session "How to connect your systems to AI Tools with MCP Servers" at the Nordic Integration Summit 2025 By Cecilia Wirén.

Overview

This MCP server provides a set of tools for interacting with an issue management system. It acts as a bridge between MCP clients and an external REST API, offering functionalities to retrieve, update, and manage issues.

Prerequisites

Before running the MCP server, ensure you have the following:

1. .NET 9.0 Runtime

• Download and install .NET 9.0

2. External Issues API

The MCP server requires a running Issues API that provides the following endpoints:

• GET /api/issues - Get all issues (optional status query parameter)
• GET /api/issues/{id} - Get issue by ID
• POST /api/issues - Create new issue
• PUT /api/issues?status={status} - Update issue status
• POST /api/issues/{id}/comments - Add comment to issue
• DELETE /api/issues/{id} - Delete issue

The API should return JSON responses with the following Issue model structure:

{
  "id": 1,
  "name": "Issue Title",
  "description": "Issue Description",
  "status": "Open", // Open, InProgress, Resolved, Closed
  "createdDate": "2024-01-01T00:00:00Z",
  "updatedDate": "2024-01-01T00:00:00Z",
  "comments": ["Comment 1", "Comment 2"]
}

Getting Started

1. Clone the Repository

git clone <repository-url>
cd MCPDemo.McpServer

2. Configure the API Base URL

Update the ApiBaseUrl in appsettings.json to point to your running Issues API:

{
  "ApiBaseUrl": "https://your-issues-api-url"
}

3. Install Dependencies

dotnet restore

4. Run the Application

dotnet run

The MCP server will start and be available for MCP client connections. In development mode, a test endpoint is available at /test to verify the server is running.

Testing with MCP Inspector

The MCP Inspector is a useful tool for testing and debugging MCP servers during development.