Surfil
// integration

Surfil consolidates any MCP server behind one endpoint

Any MCP server or MCP-based agent is consolidated behind a single Surfil endpoint - less repeated context per operation, and one interception point governing them all.

Install for MCPAll integrations →
surfil · fleet - 3 orgs · 128 devices
◇ Orgs
3
▢ Devices
128
⚑ Shadow
2 found
Northwind48 devicesenrolled
Acme Dev36 devicesenrolled
dev_77cunsanctioned MCPflagged
Where it sits

One layer in your stack

In front of your MCP servers on your device, collapsing many endpoints into one interception point you can meter and govern.

youYour MCP servers & agents
↓
surfilSurfil · one on-device interception point
↓
providerModel provider · byte-exact passthrough
ⓘ One interception point, on your device. Surfil never chains a second proxy in front of MCP agents, and passthrough to the provider is byte-exact.
What you get

What you get

Consolidate endpoints

Many MCP servers collapse into one endpoint, so agents stop re-sending the same context per operation.

Govern them together

Guard and Fleet Control screen and inventory every MCP server through the same single interception point.

Meter the value

Each signed output is one Credit; execution stays unmetered, so you meter proven value, not raw MCP traffic.

Setup

Add Surfil to MCP agents

Three steps, no config rewrite, reversible byte-for-byte.

1Install Surfil; point your agents at the one consolidated endpoint instead of many separate servers.
2Run normally for a week - Cap measures the context saved and signs the first receipt from that traffic.
3Add Guard and Fleet Control to screen and inventory the MCP servers as your usage scales up.
Install for MCPRead the docs →
What holds

Why it fits MCP

Fewer repeated contexts

One consolidated endpoint means less duplicated context shipped on every single MCP operation.

One layer, not many

Every MCP server routes through the same single interception point, never a stack of chained proxies.

Reversible byte-for-byte

A clean uninstall restores every agent and MCP config exactly, so backing it all out costs you nothing.

Works with

Every agent, the same layer

One adapter per agent, all on the same on-device interception point.

Claude Code

Between Claude Code and your model provider, on your device - one interception point, never a second proxy stacked into the path.

See adapter →

Cursor

At Cursor's MCP layer on your device: one endpoint for its MCP servers today, with full-traffic interception on the roadmap via the network layer.

See adapter →

Codex

One adapter under Codex, on your device - the same interception point every other agent uses, never a stacked second layer.

See adapter →

Copilot

Beside Copilot on your device: detected, with its MCP connected where a host exposes it. Its GitHub-proxied completions are not redirectable today.

See adapter →

Add Surfil to MCP agents

Core installs beside the agents you already run, byte-exact, and the first signed receipt arrives after one normal week of traffic.

Install for MCPAll integrations