MCP Servers
Run MCP servers as microVMs that wake in milliseconds when an agent calls them, and cost nothing between calls.
Tools with expensive initialisation (indexes, model loads, browsers) are snapshotted warm and resumed on the call.
Agent traffic is bursty and mostly idle. A server that isn't being called isn't running, and isn't billed.
One isolated server per agent, per tool or per tenant, rather than one shared process handling everyone.
Calls a tool when the agent needs it
Filters traffic, injects the secrets; servers never hold them
Under the hood
The platform features this use case is built on.
Bulky tools start and resume in milliseconds, and consume nothing between tool calls.
Injects secrets so the MCP server itself never has access to them, and filters its outbound traffic.
Sign up to Unikraft Cloud and follow the guide to run your first MCP server