FortMesa company logo
    Login
    Back to Saferoom

    SAFEROOM INSTALLATION

    Installation paths

    Your security program, wherever you already work.

    Primary Deployments

    Claude Connector

    Works with Claude.ai & Claude Code

    1. 1

      Settings → Connectors → Browse connectors

    2. 2

      Find FortMesa and connect

    3. 3

      Sign in with FortMesa

    Nothing to install. Document uploads require clearlisting https://mcp.fortmesa.com if you filter outbound traffic.

    .vsix (IDE Extension)

    Works with Claude Code, Codex, Cursor, GitHub Copilot, Antigravity

    1. 1

      Install FortMesa Saferoom from your editor's extension marketplace

    2. 2

      Open the FortMesa view in the activity bar → Sign In

    3. 3

      Ask your agent about your controls

    The extension registers the fortmesa server with every agent it finds, and keeps them in sync when you change scope or environment.

    For Visual Studio Code

    Visual Studio Marketplace

    For Other IDEs

    OpenVSX Registry

    .mcpb (MCP Bundle)

    Works with Claude Desktop

    1. 1

      Download the FortMesa Saferoom .mcpb file from the latest release

    2. 2

      Open it — Claude Desktop installs the bundle

    3. 3

      Sign in when prompted

    The bundle is self-contained — updates ship as new releases. Your token stays in ~/.fmcode/credentials.json.

    What you need

    Node.js 24+
    VS Code 1.102+ for the extension
    A FortMesa account

    What you get

    Files land where you point them.

    Saferoom does the transfer itself — name a path, get a file. Switch to Network mode and the agent fetches signed links instead, which needs an HTTP client on its end.

    Fence the blast radius.

    Lock the agent to one scope, a named set, or leave it open. Turn any tool off and it disappears from the agent's list — and is refused if the agent asks for it by name anyway. Local install only.

    Watch it work.

    The Event viewer is a live timeline of every call: tool, scope, outcome, duration. No payloads, no file paths, no tokens — not filtered out, never collected. Nothing written to disk.

    Change your mind without restarting.

    Switch environment, scope or tool selection and every connected agent picks it up straight away.

    OAuth 2.0 with PKCE.

    Your token lands in ~/.fmcode/credentials.json at 0600 and never leaves the machine.