MCP Fusion/Operate and integrate/Self hosting

Self hosting

Ask AI about Vinkius

Run the same MCP Fusion server on Vercel, Cloudflare Workers or AWS: adapters keep the tools, middleware and Presenters unchanged, with your own account and your own bill.

Every MCP Fusion server deploys unchanged to your own infrastructure. The adapters wrap your registry in a platform specific handler, and the tools, middleware and Presenters are untouched. This page covers the escape hatch; for most connectors the free path in Deploy is the shortest.

Vercel

bash

npm install @mcpfusion/vercel

typescript

// app/api/mcp/route.ts
import { vercelAdapter } from '@mcpfusion/vercel';
import registry from './registry';

export const POST = vercelAdapter<AppContext>({
  registry,
  contextFactory: async (extra) => ({ ... }),
});

export const runtime = 'edge';

Then vercel deploy. Setting runtime = 'edge' keeps the per request isolate model.

Cloudflare Workers

bash

npm install @mcpfusion/cloudflare

typescript

import { cloudflareWorkersAdapter } from '@mcpfusion/cloudflare';

export default cloudflareWorkersAdapter({
  registry,
  contextFactory: async (extra) => ({ ... }),
});

Workers bindings plug into the adapter: D1 for storage, KV for the FSM state store, R2 for objects. Each request runs in its own isolate.

AWS

bash

npm install @mcpfusion/aws

The AWS connector works in both directions:

createLambdaAdapter and createSfnAdapter expose Lambda functions and Step Functions state machines as MCP tools through a resource tagging convention
defineAwsTool(name, client, config) defines typed tools that call AWS services
MVA interception shapes the Lambda payloads before they reach the agent

What you trade

	Vinkius Cloud	Self hosting
Cost	Free hosting	Your account, your bill
Security layers	DLP, kill switch, audit trail, rate limiter, circuit breaker included	You assemble equivalents yourself
Console	Capabilities, credentials, cost, monitoring wired in	Build your own observability
Deploys	`mcpfusion deploy`	Platform specific pipelines
Scaling	Auto scaling on the Edge	Platform dependent

The adapters are first class, not a fallback. Some connectors belong inside an existing Vercel or Cloudflare application, and MCP Fusion keeps the same code, middleware and Presenters there. What changes is who operates the perimeter.

Compliance note

Fusion blocks PII locally by default wherever the server runs, so the egress firewall is yours on any platform. The tamper proof audit trail and the kill switch are Vinkius Cloud features; self hosted deployments need their own equivalents if a compliance review demands them.

Next steps

Deploy: the free managed path
Governance: the lockfile works on any platform
CLI: local commands stay the same everywhere