---
title: "Saferoom Installation Paths"
source: "/saferoom/installation-paths"
---

# Saferoom Installation Paths

_SAFEROOM INSTALLATION_

### Installation paths

Your security program, wherever you already work.

[Back to Saferoom](/saferoom#install)

### Scope limiting

Multi-tenant users may limit the agent’s access to specific customers.

### Primary Deployments

#### Claude Connector

Works with Claude.ai & Claude Code

##### Links

- **Connect to Claude** — https://claude.ai/directory/fortmesa

##### Steps

- Settings → Connectors → Browse connectors
- Find FortMesa and connect
- 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

##### Links

- **Visual Studio Marketplace** · **Context:** For Visual Studio Code — https://marketplace.visualstudio.com/items?itemName=fortmesa.saferoom
- **OpenVSX Registry** · **Context:** For Other IDEs — https://open-vsx.org/extension/fortmesa/saferoom

##### Steps

- Install FortMesa Saferoom from your editor's extension marketplace
- Open the FortMesa view in the activity bar → Sign In
- 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.

#### .mcpb (MCP Bundle)

Works with Claude Desktop

##### Links

- **Download latest release** — https://github.com/fortmesa/fmmcp-local/releases

##### Steps

- Download the FortMesa Saferoom .mcpb file from the latest release
- Open it — Claude Desktop installs the bundle
- Sign in when prompted

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

### What you need

### Items

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

### What you get

### Items

- **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.

## Book a Demo

#### Ready to formalize compliance?

Book a 30-minute walkthrough and see how FortMesa directs and verifies your security work, by your people and your AI.

Book a Demo

### Options

- **I'm a Service Provider** — /demo
- **I'm an Organization** — /organization-demo

---

> _Markdown mirror of `/saferoom/installation-paths` on fortmesa.com — served for AI agents and non-JavaScript crawlers. Full site index: https://fortmesa.com/llms.txt · entire site as one file: https://fortmesa.com/llms-full.txt_
