mcp.run — Portable & Secure MCP Server Hosting
A registry and runtime where developers discover, host, and securely run portable MCP servers as Wasm tools across Claude, Cursor, and other AI clients.
Code
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>mcp.run — Portable & Secure MCP Server Hosting</title>
<style>
:root {
--bg: #0b0f17;
--surface: #141a26;
--surface-2: #1b2433;
--text: #e6edf6;
--muted: #8b97a8;
--accent: #6ea8fe;
--border: rgba(255, 255, 255, 0.08);
--radius: 16px;
}
* { box-sizing: border-box; }
body {
margin: 0;
min-height: 100vh;
display: flex;
align-items: center;
justify-content: center;
padding: 24px;
background:
radial-gradient(1200px 600px at 80% -10%, rgba(110, 168, 254, 0.12), transparent 60%),
var(--bg);
color: var(--text);
font-family: "Inter", system-ui, -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
line-height: 1.55;
}
.card {
width: 100%;
max-width: 640px;
background: var(--surface);
border: 1px solid var(--border);
border-radius: var(--radius);
padding: 28px;
box-shadow:
0 1px 0 rgba(255, 255, 255, 0.04) inset,
0 24px 60px -20px rgba(0, 0, 0, 0.6);
}
.eyebrow {
display: inline-flex;
align-items: center;
gap: 8px;
font-size: 0.72rem;
font-weight: 600;
letter-spacing: 0.08em;
text-transform: uppercase;
color: var(--accent);
background: rgba(110, 168, 254, 0.1);
border: 1px solid rgba(110, 168, 254, 0.25);
padding: 5px 10px;
border-radius: 999px;
}
h1 {
margin: 16px 0 8px;
font-size: 1.6rem;
line-height: 1.2;
letter-spacing: -0.01em;
}
.desc {
margin: 0 0 20px;
color: var(--muted);
font-size: 0.98rem;
}
h2 {
margin: 22px 0 10px;
font-size: 0.82rem;
font-weight: 600;
letter-spacing: 0.06em;
text-transform: uppercase;
color: var(--muted);
}
pre {
margin: 0;
background: var(--surface-2);
border: 1px solid var(--border);
border-radius: 12px;
padding: 14px 16px;
overflow-x: auto;
}
code {
font-family: "SFMono-Regular", ui-monospace, "JetBrains Mono", Menlo, Consolas, monospace;
font-size: 0.86rem;
color: var(--text);
}
pre + pre { margin-top: 10px; }
.pills {
display: flex;
flex-wrap: wrap;
gap: 8px;
}
.pill {
font-size: 0.78rem;
color: var(--text);
background: var(--surface-2);
border: 1px solid var(--border);
padding: 6px 12px;
border-radius: 999px;
}
.cta {
display: inline-flex;
align-items: center;
gap: 8px;
margin-top: 24px;
padding: 12px 20px;
font-size: 0.95rem;
font-weight: 600;
color: #0b0f17;
background: var(--accent);
border-radius: 12px;
text-decoration: none;
transition: transform 0.12s ease, filter 0.12s ease;
}
.cta:hover { filter: brightness(1.08); transform: translateY(-1px); }
a:focus-visible,
.cta:focus-visible {
outline: 3px solid var(--accent);
outline-offset: 3px;
border-radius: 12px;
}
</style>
</head>
<body>
<main class="card">
<span class="eyebrow" aria-label="Ecosystem">MCP directories</span>
<h1>mcp.run</h1>
<p class="desc">
A registry and runtime to discover, host, and securely run portable MCP servers as
sandboxed Wasm tools across any MCP-compatible AI client.
</p>
<h2>How to access</h2>
<pre><code>https://www.mcp.run/</code></pre>
<pre><code># run the mcp.run runner
npx --yes @dylibso/mcpx@latest</code></pre>
<h2>Compatible with</h2>
<div class="pills">
<span class="pill">Claude Code</span>
<span class="pill">Claude Desktop</span>
<span class="pill">Cursor</span>
<span class="pill">Any MCP client</span>
</div>
<a class="cta" href="https://www.mcp.run/" target="_blank" rel="noopener">
Open mcp.run
<span aria-hidden="true">→</span>
</a>
</main>
</body>
</html>What it is
mcp.run is a registry and runtime for Model Context Protocol (MCP) servers. Instead of installing a separate server binary per machine, you browse a catalog of tools (“servlets”), then run them through a single portable runtime. Servers are packaged as sandboxed WebAssembly, which makes them portable across operating systems and safer to run because each tool executes inside an isolated boundary with explicitly granted permissions.
It belongs to the MCP directories ecosystem: a place to discover capabilities and wire them into any MCP-compatible AI client rather than a single plugin.
How to access / install
Browse and manage tools in the web app:
https://www.mcp.run/
Connect your AI client to mcp.run using the mcpx runner. A typical client config points the
MCP transport at the local runner, which proxies the servlets you have installed:
# install / run the mcp.run runner (mcpx)
npx --yes @dylibso/mcpx@latest
// example MCP client config (e.g. Claude Desktop / Cursor)
{
"mcpServers": {
"mcprun": {
"command": "npx",
"args": ["--yes", "@dylibso/mcpx@latest", "run"]
}
}
}
After connecting, install tools from the catalog in the web UI and they become available to your agent through the single mcprun endpoint. Always confirm exact commands and config keys against the official docs, since runner names and flags evolve.
Good for
- Discovering MCP servers and tools from one searchable catalog.
- Running the same set of tools across multiple machines and AI clients without per-host setup.
- Teams that want sandboxed, permissioned execution rather than running arbitrary server processes directly on developer machines.