Runiq.Mcp 0.1.0-preview.7

Runiq.Mcp

MCP server integration for ASP.NET Core applications.

Runiq.Mcp lets an ASP.NET Core application expose its application services as MCP-compatible tools. Use it to turn existing C# services into tools that can be called by MCP-compatible clients without rewriting your application around a separate runtime.

Why Runiq.Mcp?

Runiq.Mcp is designed for .NET developers who want to expose application capabilities through the Model Context Protocol while staying inside the ASP.NET Core hosting and dependency injection model.

It focuses on:

• ASP.NET Core native MCP server hosting
• Dependency-injection friendly MCP tools
• Existing application service reuse
• Minimal endpoint mapping
• Streamable HTTP transport support
• Simple integration with existing ASP.NET Core applications

Install

dotnet add package Runiq.Mcp --prerelease

Quick Start

Register MCP services:

builder.Services.AddRuniqMcp();

Map the MCP endpoint:

var app = builder.Build();

app.MapRuniqMcp();

app.Run();

By default, the MCP endpoint is available at:

/mcp

Custom Endpoint Path

You can expose the MCP endpoint under a custom path:

app.MapRuniqMcp("/ai/mcp");

Example endpoint paths:

/mcp
/ai/mcp
/dashboard/api/mcp

Create an MCP Tool

MCP tools can use regular ASP.NET Core dependency injection services.

using ModelContextProtocol.Server;
using System.ComponentModel;

[McpServerToolType]
public sealed class OrderStatusMcpTool
{
    private readonly IOrderService _orders;

    public OrderStatusMcpTool(IOrderService orders)
    {
        _orders = orders;
    }

    [McpServerTool]
    [Description("Gets the current status of an order.")]
    public Task<OrderStatusResult> GetOrderStatus(
        [Description("The order identifier.")] string orderId)
    {
        return _orders.GetStatusAsync(orderId);
    }
}

Register your application service as usual:

builder.Services.AddScoped<IOrderService, OrderService>();

Then register and map Runiq MCP:

builder.Services.AddRuniqMcp();

var app = builder.Build();

app.MapRuniqMcp();

app.Run();

Minimal Example

using ModelContextProtocol.Server;
using Runiq.Mcp;
using System.ComponentModel;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddScoped<IOrderService, OrderService>();
builder.Services.AddRuniqMcp();

var app = builder.Build();

app.MapRuniqMcp();

app.Run();

public interface IOrderService
{
    Task<OrderStatusResult> GetStatusAsync(string orderId);
}

public sealed class OrderService : IOrderService
{
    public Task<OrderStatusResult> GetStatusAsync(string orderId)
    {
        return Task.FromResult(
            new OrderStatusResult(orderId, "Processing"));
    }
}

public sealed record OrderStatusResult(string OrderId, string Status);

[McpServerToolType]
public sealed class OrderStatusMcpTool
{
    private readonly IOrderService _orders;

    public OrderStatusMcpTool(IOrderService orders)
    {
        _orders = orders;
    }

    [McpServerTool]
    [Description("Gets the current status of an order.")]
    public Task<OrderStatusResult> GetOrderStatus(
        [Description("The order identifier.")] string orderId)
    {
        return _orders.GetStatusAsync(orderId);
    }
}

What This Enables

Runiq.Mcp allows your application services to become MCP tools.

ASP.NET Core service
        ↓
Runiq.Mcp
        ↓
MCP-compatible tool
        ↓
MCP client

This means you can expose existing business capabilities such as:

• Order lookup
• Customer support actions
• Travel planning services
• Internal automation services
• Reporting and analytics functions
• Domain-specific application tools

without moving those capabilities out of your ASP.NET Core application.

Typical Use Cases

Use Runiq.Mcp when you want to:

• Add an MCP server endpoint to an ASP.NET Core app
• Expose existing C# services as MCP tools
• Reuse ASP.NET Core dependency injection
• Keep tool implementation close to application logic
• Connect your application to MCP-compatible clients
• Build AI-accessible APIs without creating a separate tool server

Current Scope

The current preview focuses on MCP tools.

Planned areas:

• MCP resources
• MCP prompts
• Runiq native tool exposure
• MCP client integration
• Dashboard visibility for MCP endpoint status

Related Packages

Runiq.Net is modular. Runiq.Mcp can be used together with other Runiq packages:

Documentation

Full documentation is available at:

https://runiq.net/docs

Status

Runiq.Net is currently in preview.

APIs may change before the first stable release.

The main direction is clear:

Expose ASP.NET Core services as MCP-compatible tools and connect them with the broader Runiq.Net agent runtime.

License

MIT