MCP Server Scf

mcp-server-scf

Security compliance controls, frameworks, and risk management for AI agents.

Give your AI assistant access to 1,451 SCF security controls, 354+ framework mappings (NIST 800-53, ISO 27001, SOC 2, FedRAMP, GDPR), evidence tracking, risk registers, and vendor risk management — all through the Model Context Protocol.

Built for the [SCF Controls Platform](https://scfcontrolsplatform.com/). Maintained by ComplianceGenie.io.

🆕 The platform is now open-source, self-hosted software. The SCF Controls Platform — SCF-native GRC tooling for the free Secure Controls Framework content — is published under AGPL-3.0 at [scf-controls-platform-oss](https://github.com/MarkAC007/scf-controls-platform-oss). Companies download and host it themselves via Docker Compose.

Having trouble? → docs/troubleshooting.md · API key setup → docs/authentication.md · How it works → docs/architecture.md

---

Overview

mcp-server-scf connects AI assistants to the SCF Controls Platform via MCP, enabling natural language interaction with your compliance program. Your AI can browse the full SCF control catalog, track implementation progress, manage evidence collection, assess risks, and monitor third-party vendors — all without leaving your editor or chat.

42 tools over 225 platform operations, in 16 groups. Each tool is one noun and direction — scf_vendor_read, scf_vendor_write — and its method argument picks the operation; the method description explains each one. Read tools are readOnlyHint: true, so a client can allow them all at once.

Only the core groups are in the tool list at startup (26 tools, about 27k tokens of schema instead of 71k). Call scf_load_tools with the groups you need — or all — and the rest appear; the server sends notifications/tools/list_changed. A client that ignores that notification can set SCF_LOAD_ALL_TOOLS=true to get everything up front. Per-group docs list every method with its parameters; docs/migration-consolidation.md maps each pre-v4 tool name to its tool and method.

Try it with MCP Inspector

Kick the tires without adding the server to a client — MCP Inspector launches a local UI that introspects every tool, its schema, and its description:

npx @modelcontextprotocol/inspector npx -y mcp-server-scf

Inspector opens on http://localhost:6274 and connects to mcp-server-scf over stdio. You'll see the 26 core tools (set SCF_LOAD_ALL_TOOLS=true for all 42), each with a method picker and its Zod schema rendered as a live form.

Live tool calls need your instance's URL and an API key — export SCF_API_URL and SCF_API_KEY in the same shell before launching Inspector, or set them under the "Environment Variables" tab inside the Inspector UI. Without them, you can still browse schemas and descriptions; tool calls return a configuration error.

---

Quick Start

1. Self-host the platform & get an API key

The SCF Controls Platform is open-source software you host yourself — there is no sign-up. Deploy it from scf-controls-platform-oss (a Docker Compose stack with bundled PostgreSQL, Redis, and MinIO), then:

1. Set an API_KEY in the platform's .env (generate one with openssl rand -hex 32), or create a key in Settings → API Keys once the app is running.
2. Note your instance's API URL — http://localhost:8000 by default, or your deployed host.

Use that key as SCF_API_KEY and the instance URL as SCF_API_URL (see Configuration).

2. Install — one-click

Pick the route for your client.

Claude Desktop — the one-click path is the signed [.mcpb Desktop Extension](#claude-desktop-extension-mcpb) below. Claude Desktop does not register a custom URL scheme, so there is no clickable deeplink; instead you drag the .mcpb onto Settings → Extensions and paste your API key once. See anthropics/claude-code#26952 for the upstream tracking issue.

Cursor — click the badge below. Cursor registers the cursor:// scheme, so the deeplink opens the IDE with the server config pre-filled:

After install, edit the pre-filled SCF_API_URL to point at your instance — there is no hosted default.

Prefer to edit config by hand, or on a client without a deeplink (Windsurf, Docker)? See [3. Manual config](#3-manual-config) below.

Claude Desktop Extension (.mcpb)

For Claude Desktop ≥ 0.11.0, the easiest install is a signed .mcpb bundle — no JSON editing, no npx runtime, no Node required on the host:

1. Download mcp-server-scf- .mcpb from the latest GitHub release.
2. Double-click the file (or drag it onto Claude Desktop → Settings → Extensions).
3. When prompted, paste your scf_… API key. It's stored in your OS keychain, not in a config file.
4. Claude Desktop restarts the server and the core tools are avai