MCPOverview

Overview

Understand how Runiq.Mcp helps ASP.NET Core developers expose application services as MCP tools.

Runiq.Mcp allows ASP.NET Core applications to expose selected application services as MCP tools.

Instead of building a separate MCP server from scratch, developers can reuse their existing .NET services, dependency injection setup, and application logic, then expose only the capabilities they choose through a standard /mcp endpoint.

This makes existing .NET applications easier to connect with MCP-compatible AI clients and agent environments.

Runiq.Mcp connecting an existing ASP.NET Core application to MCP-compatible AI clients

Install the package

Add the MCP package to the ASP.NET Core project that will expose the /mcp endpoint:

.NET CLI
dotnet add package Runiq.Mcp --prerelease

Use this package when your application needs to expose selected ASP.NET Core services as MCP tools.

What developers get

Developer needRuniq.Mcp benefit
Expose existing .NET behavior to AI clientsTurn selected application services into MCP tools.
Keep business logic where it already livesUse normal ASP.NET Core dependency injection and services.
Avoid a second server projectHost the MCP endpoint from the same ASP.NET Core app.
Keep the exposed surface smallPublish only classes and methods marked as MCP tools.
Test exposed capabilities quicklyUse the Runiq Dashboard to list and run MCP tools.

The important idea is control. Your application owns the service, the method, the input shape, and the returned result. MCP-compatible clients only see the tool boundary you decide to expose.

How this section is organized

PageWhat it covers
Creating an MCP serverAdd Runiq.Mcp and map the /mcp endpoint.
Application service as MCP toolWrap an existing ASP.NET Core service with a typed MCP tool class.
Studio testingList and run exposed MCP tools through the embedded Runiq Studio.

The Runiq.ContextTravelGuide sample is used throughout this section because it shows the common developer path: take an existing ASP.NET Core service, wrap it with a small MCP tool class, run the application, and test the tool through the dashboard.

On this page