MCP Fusion/Operate and integrate/Deploy

Deploy

Ask AI about Vinkius

Ship your MCP Fusion connector to Vinkius Cloud with totally free hosting: mcpfusion deploy bundles it, the Edge provisions a V8 isolate and the security layers arm themselves. No credit card required.

This is the page the whole framework exists for. mcpfusion deploy takes the server on your laptop and turns it into a live connector on the Vinkius Edge: totally free hosting, no credit card, no infrastructure to manage. Your connector runs on the same global infrastructure, behind the same security layers, as every other connector in the platform.

Deploy · local to Edge

One command from your laptop to a live connector. Click a step or press Run.

$ mcpfusion deploy

mcpfusion deploy

  ✓ resolving entry ./src/server.ts
  ✓ bundling with esbuild (312 KB)
  ✓ tree-shaking node_modules
  ✓ verifying fusion.lock (12 tools)

Your server, its presenters and its capability lockfile travel together. Nothing drifts between what you tested and what ships.

Step 1 of 5

mcpfusion deploy, step by step. Press Run and follow one deploy: the server bundles, compresses and uploads, a V8 isolate provisions on the Edge, the security layers arm themselves and a connection token comes back. Under a minute from your laptop to a live connector.

Press Run and watch one deploy end to end: bundle, upload, V8 isolate, security layers, connection token.

The one command

bash

mcpfusion deploy

The CLI bundles your server with esbuild, compresses it, uploads it and provisions a sealed V8 isolate on the Vinkius Edge. Cold starts stay fast, and the isolate has no process spawning, no filesystem and no network egress unless you allow it.

Security layers turn on with the deploy

Writing nothing, you get all of this enabled on arrival:

Layer	What it does
DLP engine	PII redaction on egress, powered by your Presenters
Egress firewall	Sensitive fields blocked at the wire
Kill switch	One click halt from the console, backed by Circuit breaker thinking
Audit trail	Tamper proof, cryptographically signed records
Rate limiter	Per token request throttling
Circuit breaker	Automatic isolation of failing upstreams
Token auth	Every call authenticated with the connection token

The same protections the console documents for every connector, see Security posture and DLP protection.

What comes back

The deploy finishes with a connection token and an MCP URL in the shape https://edge.vinkius.com/vk_<token>/mcp. Paste it into Claude Desktop, Cursor, VS Code or any MCP client. Your connector now shows up in the Vinkius console like every other connector:

AI Capabilities listed and toggleable, see AI Capabilities
Credentials form for your buyers, see Credentials
Live monitoring in Dashboard, traffic and reliability in Server traffic and Tool reliability
Cost attribution in AI spend

Hosting is free. There is no credit card step, no trial clock and no server bill. Build the connector, deploy it, share the MCP URL. That is the whole loop.

Pairing with the CLI

bash

mcpfusion remote --server-id <id> --token <token>
mcpfusion token <token>

remote links a deployed connector to your local project for follow up deploys, and token stores the connection token for client configuration.

Free locally, free on the Edge

Fusion blocks PII locally by default, so development has the same egress firewall as production. When you need compliance proof for SOC2, GDPR or HIPAA reviews, the Edge adds tamper proof audit logs and the kill switch, still free.

Self hosting exists, hosting free is unique

The same server deploys unchanged to Vercel or Cloudflare with the adapters in Self hosting. You trade the included security layers and the console integration for your own account and your own bill. For everything from a first prototype to production, mcpfusion deploy is the shortest path: one command, zero cost.

Next steps

CLI: every deploy related command
Governance: lock the surface before you ship
Credentials: let buyers bring their own keys