Studio testing

Use the Runiq Dashboard to verify that the ASP.NET Core application exposes the expected MCP tools.

The goal is simple: run the application, open the dashboard, list MCP tools, and execute one tool call.

Enable Studio

using Runiq.Core;

var app = builder.Build();

app.UseRuniqDashboard(options =>
{
    options.Path = "/dashboard";
    options.Title = "Runiq MCP Travel Guide";
    options.Authentication(auth =>
    {
        // Demo/sample only. Do not use AllowAnonymous in production.
        auth.AllowAnonymous();
    });
});

app.MapRuniqMcp();

app.Run();

The default dashboard path is /runiq. If you set Path = "/dashboard", open /dashboard in the same host application.

List MCP tools

The MCP tools list confirms that the host application discovered the expected tool methods and exposed their names, descriptions, and input contracts to MCP clients.

For the travel sample, you should see a tool such as:

create_travel_summary

If the tool is missing, check that:

• the application is running,
• AddRuniqMcp() is registered,
• MapRuniqMcp() is mapped,
• the tool class has [McpServerToolType],
• the method has [McpServerTool].

Run an MCP tool

The run view lets developers provide input values and execute the selected MCP tool through the same runtime boundary that MCP clients use.

Example input:

This validates the full hosted flow: dependency injection, input binding, service execution, typed results, and error handling.