MCP
Make your C# application services available to MCP-compatible clients.
MCP gives external AI clients a way to discover and call selected application capabilities. Runiq hosts the MCP server inside ASP.NET Core, alongside your existing services and dependency injection.
Start with one capability
Install the server integration in your host project:
Define an attributed tool, register its service dependencies, and map the endpoint. The default route is /mcp, using stateless Streamable HTTP.
Choose the tool boundary
| Capability | How it is made available |
|---|---|
| Runiq agent tool | Attach an AgentTool<TInput, TOutput> to an agent. |
| MCP tool | Expose an attributed method for MCP-compatible clients. |
| Application service | Reuse it through either adapter and dependency injection. |
Registering an agent tool does not automatically publish it through MCP. This integration exposes a server; it does not attach a remote MCP server to your agents.
Build and verify
| Guide | Outcome |
|---|---|
| Creating an MCP server | Register transport and choose an endpoint. |
| Application service as a tool | Build a complete C# tool backed by a service. |
| Studio testing | Inspect the tool locally, then verify the MCP connection. |