mcp-remote (local) logo

mcp-remote (local)

Beta

A bridge that fronts a remote MCP server for clients that only speak stdio. The address on its command line decides what it reaches.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Glen Maddern

How it works

Every agent request passes through Ferentin policy before it reaches mcp-remote (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y mcp-remote.

Ferentin's endpoint agent finds mcp-remote (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. mcp-remote (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About mcp-remote (local)

A bridge that fronts a remote MCP server for clients that only speak stdio. The address on its command line decides what it reaches.

Frequently asked about mcp-remote (local)

How do I connect mcp-remote (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add mcp-remote (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the mcp-remote (local) integration generally available?
The mcp-remote (local) integration is currently beta on Ferentin.