Surfil
// integration

Surfil connects to Cursor through MCP

Surfil consolidates the MCP servers Cursor uses into one interception point and gives Cursor portable memory, without changing how you use it. Cursor's own model calls run through Cursor's backend; full traffic interception arrives with Surfil's on-device network layer.

Install for CursorAll integrations →
surfil · your control plane
▤ Saved / mo
$412
⛨ Blocked
27
≋ Memory
94%
Savings trendsigned
Trend, last 12 points
✓rcpt_8f2aepoch 7 · offlineVALID
!AWS key in payloadacme/apiblocked
Where it sits

One layer in your stack

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.

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

What you get today

Consolidate MCP

Cursor's MCP servers collapse into one endpoint, so less repeated context ships per operation.

Govern MCP calls

Guard screens the MCP tool calls Surfil sees, catching secrets and injection before they run.

Portable memory

Mind gives Cursor local memory with provenance through MCP that follows you to your other agents.

Setup

Add Surfil to Cursor

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

1Install Surfil; it detects Cursor and connects its MCP servers with no change to how you use it.
2Keep working as normal; Cursor's MCP now routes through one governed, consolidated endpoint.
3Turn on Guard enforce once the simulation report proves the block-list is right for your team.
Install for CursorRead the docs →
What holds

Why it fits Cursor

MCP consolidated

Cursor's MCP servers collapse to one endpoint, so less repeated context ships per operation.

No workflow change

You use Cursor exactly as before; Surfil connects underneath through MCP, reversibly.

Reversible byte-for-byte

A clean uninstall restores every Cursor config exactly, so backing 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 →

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 →

MCP agents

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

See adapter →

Add Surfil to Cursor

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

Install for CursorAll integrations