\n\n# mcp-server-scf\n\n\n\n[](https://github.com/MarkAC007/mcp-server-scf/actions/workflows/ci.yml)\n[](https://github.com/MarkAC007/mcp-server-scf/actions/workflows/security.yml)\n[](https://scorecard.dev/viewer/?uri=github.com/MarkAC007/mcp-server-scf)\n[](https://socket.dev/npm/package/mcp-server-scf)\n\n\n\n[](https://www.npmjs.com/package/mcp-server-scf)\n[](https://www.npmjs.com/package/mcp-server-scf)\n[](https://packagephobia.com/result?p=mcp-server-scf)\n[](LICENSE)\n[](https://modelcontextprotocol.io)\n\n\n\n[](https://registry.modelcontextprotocol.io/v0/servers?search=scfcontrolsplatform)\n\n\n\n\n\n\n**Security compliance controls, frameworks, and risk management for AI agents.**\n\nGive 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](https://modelcontextprotocol.io).\n\nBuilt for the **[SCF Controls Platform](https://scfcontrolsplatform.com/)**. Maintained by [ComplianceGenie.io](https://compliancegenie.io).\n\n> 🆕 **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.\n\n> Having trouble? → [**docs/troubleshooting.md**](docs/troubleshooting.md) · API key setup → [**docs/authentication.md**](docs/authentication.md) · How it works → [**docs/architecture.md**](docs/architecture.md)\n\n---\n\n## Overview\n\n`mcp-server-scf` connects AI assistants to the [SCF Controls Platform](https://scfcontrolsplatform.com/) 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.\n\n**196 tools** across 14 domains — click through for full parameter tables and example prompts:\n\n| Domain | Tools | Description |\n| -------------------------------------------------------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| [Catalog](docs/tools/catalog.md) | 8 | Browse 1,451 controls, 354+ frameworks, 5,736 assessment objectives, domains and evidence definitions |\n| [Control Scoping](docs/tools/scoped-controls.md) | 10 | Track implementation status across an 8-state workflow; bulk scope and unscope by framework; framework coverage, scope-change preview and per-control overrides |\n| [Evidence](docs/tools/evidence.md) | 41 | Evidence tracking (single + batch), tasks, file review, health, validation, AI assessments and review queues |\n| [Risk Management](docs/tools/risk.md) | 17 | 5x5 risk matrix, risk register, scoring updates, custom risks, control↔risk traceability, risk profile |\n| [Vendor Risk (TPRM)](docs/tools/vendors.md) | 23 | Vendor registry, AI research and assessments, certifications, action items, compensating controls |\n| [Organization](docs/tools/organization.md) | 10 | Users, orgs, audit trail, change cursor, work queues, notifications |\n| [Capabilities](docs/tools/capabilities.md) | 19 | KSI themes, scorecards, evidence posture, systems inventory, system evidence capabilities, catalog + AI recipes |\n| [Webhooks](docs/tools/webhooks.md) | 6 | Webhook endpoints, delivery logs, secret rotation |\n| [Documents](docs/tools/documents.md) | 15 | ISMS document generation, section editing, merge resolution, lifecycle transitions, export |\n| [Audit Engagements](docs/tools/engagements.md) | 16 | Engagement workspaces, frozen scope, framework-native presentation, auditor access, structured queries |\n| [Catalog Reconciliation](docs/tools/catalog-reconciliation.md) | 9 | Preview, decide, apply and roll back an SCF catalog version upgrade for your org |\n| [Teams](docs/tools/teams.md) | 11 | Business functions, teams and rosters, team accountability for controls and evidence (single + batch) |\n| [Collaboration](docs/tools/collaboration.md) | 7 | User assignments to controls, evidence and tasks; comment threads |\n| [Guided Journey](docs/tools/journey.md) | 4 | The staged path an organisation walks, journey templates, import, and named stage attestation |\n\nWhich platform operations became tools, which are deferred, and which stay out on purpose is recorded in [docs/tool-scope.md](docs/tool-scope.md).\n\n---\n\n## Try it with MCP Inspector\n\nKick the tires without adding the server to a client — [MCP Inspector](https://github.com/modelcontextprotocol/inspector) launches a local UI that introspects every tool, its schema, and its description:\n\n```bash\nnpx @modelcontextprotocol/inspector npx -y mcp-server-scf\n```\n\nInspector opens on `http://localhost:6274` and connects to `mcp-server-scf` over stdio. You'll see all 196 tools, grouped by domain, with their Zod schemas rendered as a live form.\n\nLive 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.\n\n---\n\n## Quick Start\n\n### 1. Self-host the platform & get an API key\n\nThe SCF Controls Platform is **open-source software you host yourself** — there is no sign-up. Deploy it from [scf-controls-platform-oss](https://github.com/MarkAC007/scf-controls-platform-oss) (a Docker Compose stack with bundled PostgreSQL, Redis, and MinIO), then:\n\n1. 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.\n2. Note your instance's API URL — `http://localhost:8000` by default, or your deployed host.\n\nUse that key as `SCF_API_KEY` and the instance URL as `SCF_API_URL` (see [Configuration](#configuration)).\n\n### 2. Install — one-click\n\nPick the route for your client.\n\n**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](https://github.com/anthropics/claude-code/issues/26952) for the upstream tracking issue.\n\n**Cursor** — click the badge below. Cursor registers the `cursor://` scheme, so the deeplink opens the IDE with the server config pre-filled:\n\n[](cursor://anysphere.cursor-deeplink/mcp/install?name=scf&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIm1jcC1zZXJ2ZXItc2NmIl0sImVudiI6eyJTQ0ZfQVBJX0tFWSI6InNjZl95b3VyX2FwaV9rZXlfaGVyZSIsIlNDRl9BUElfVVJMIjoiaHR0cDovL2xvY2FsaG9zdDo4MDAwIn19)\n\nAfter install, edit the pre-filled `SCF_API_URL` to point at **your** instance — there is no hosted default.\n\nPrefer to edit config by hand, or on a client without a deeplink (Windsurf, Docker)? See **[3. Manual config](#3-manual-config)** below.\n\n### Claude Desktop Extension (.mcpb)\n\nFor 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:\n\n1. Download `mcp-server-scf-.mcpb` from the [latest GitHub release](https://github.com/MarkAC007/mcp-server-scf/releases/latest).\n2. Double-click the file (or drag it onto Claude Desktop → **Settings → Extensions**).\n3. When prompted, paste your `scf_…` API key. It's stored in your OS keychain, not in a config file.\n4. Claude Desktop restarts the server and all 196 tools are available.\n\nTo uninstall or update the API key later: **Settings → Extensions → SCF Controls Platform → Configure**.\n\n### 3. Manual config\n\n**Claude Desktop** — edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\\Claude\\claude_desktop_config.json` (Windows):\n\n```json\n{\n \"mcpServers\": {\n \"scf\": {\n \"command\": \"npx\",\n \"args\": [\"-y\", \"mcp-server-scf\"],\n \"env\": {\n \"SCF_API_KEY\": \"your_api_key_here\",\n \"SCF_API_URL\": \"http://localhost:8000\"\n }\n }\n }\n}\n```\n\n**Claude Code:**\n\n```bash\nclaude mcp add scf -- npx -y mcp-server-scf\nexport SCF_API_KEY=\"your_api_key_here\"\nexport SCF_API_URL=\"http://localhost:8000\"\n```\n\n**Cursor / Windsurf** — same JSON shape as Claude Desktop in `.cursor/mcp.json` (or the equivalent Windsurf path).\n\n**Docker:**\n\n```json\n{\n \"mcpServers\": {\n \"scf\": {\n \"command\": \"docker\",\n \"args\": [\"run\", \"-i\", \"--rm\", \"-e\", \"SCF_API_KEY\", \"-e\", \"SCF_API_URL\", \"markac007/mcp-server-scf\"],\n \"env\": {\n \"SCF_API_KEY\": \"scf_your_api_key_here\",\n \"SCF_API_URL\": \"https://scf.your-domain.example\"\n }\n }\n }\n}\n```\n\n---\n\n## Configuration\n\n| Variable | Required | Default | Description |\n| ------------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------------ |\n| `SCF_API_KEY` | Yes | — | API key from your self-hosted platform instance |\n| `SCF_API_URL` | Yes | — | Base URL of your self-hosted platform (e.g. `http://localhost:8000`). The former hosted default is decommissioned. |\n\n---\n\n## Example Prompts\n\nOnce connected, try asking your AI assistant:\n\n- \"What NIST 800-53 controls apply to access control?\"\n- \"Show me my organization's control implementation progress.\"\n- \"List all critical vendors and their risk scores.\"\n- \"Create a risk assessment for our cloud migration.\"\n- \"What evidence do I need to collect for SOC 2 audit?\"\n- \"Show the 5x5 risk matrix for my organization.\"\n- \"Run a DPSIA on our cloud provider vendor.\"\n\nMore examples live in each per-domain doc under [`docs/tools/`](docs/tools/).\n\n---\n\n## Documentation\n\n- [**docs/authentication.md**](docs/authentication.md) — API key setup, rotation, self-hosted URL configuration, scopes.\n- [**docs/architecture.md**](docs/architecture.md) — request flow, error model, rate limiting, what the server does and does not do.\n- [**docs/troubleshooting.md**](docs/troubleshooting.md) — symptom/cause/fix for the common failure modes.\n- [**docs/tools/**](docs/tools/) — per-domain reference with full parameter tables.\n\n---\n\n## Security\n\n- API keys are never logged or included in error messages.\n- Keys are SHA-256 hashed server-side. Use HTTPS for any instance reachable beyond localhost.\n- Rate limiting: 100 req/min read, 20 req/min write.\n- Multi-tenant — all operations scoped to your organization.\n- npm package published with [provenance attestation](https://docs.npmjs.com/generating-provenance-statements) via OIDC trusted publishing.\n- CI includes Gitleaks secret detection, CodeQL analysis, and Semgrep SAST.\n\nSee [SECURITY.md](SECURITY.md) to report a vulnerability.\n\n---\n\n## Privacy Policy\n\n`mcp-server-scf` is a stateless connector — it stores no user data itself. All data flows directly between your MCP client and your own SCF Controls Platform instance, authenticated with your API key; nothing is sent to, or retained by, any third party. See the full [privacy policy](https://scfcontrolsplatform.com/privacy) for details.\n\n---\n\n## Development\n\n```bash\ngit clone https://github.com/MarkAC007/mcp-server-scf.git\ncd mcp-server-scf\nnpm install\nnpm run build\nnpm run dev # Watch mode\nnpm run lint # ESLint\nnpm test # Vitest\n```\n\n### Testing with MCP Inspector\n\n```bash\nSCF_API_KEY=scf_your_key npx @modelcontextprotocol/inspector node build/index.js\n```\n\n---\n\n## Contributing\n\nContributions welcome! Please read [CONTRIBUTING.md](CONTRIBUTING.md) before submitting PRs.\n\nThis project follows the [Contributor Covenant](https://www.contributor-covenant.org/) — see [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.\n\n1. Fork the repository\n2. Create your feature branch (`git checkout -b feature/amazing-feature`)\n3. Commit your changes (`git commit -m 'Add amazing feature'`)\n4. Push to the branch (`git push origin feature/amazing-feature`)\n5. Open a Pull Request\n\n---\n\n## License\n\nMIT — see [LICENSE](LICENSE).\n\n---\n\n## Links\n\n- [scf-controls-platform-oss](https://github.com/MarkAC007/scf-controls-platform-oss) — the open-source, self-hosted platform (AGPL-3.0)\n- [ComplianceGenie.io](https://compliancegenie.io) — maintainer\n- [Model Context Protocol](https://modelcontextprotocol.io) — MCP specification\n- [SCF Framework](https://securecontrolsframework.com) — Secure Controls Framework\n- [npm Package](https://www.npmjs.com/package/mcp-server-scf) — npm registry\n- [Changelog](CHANGELOG.md) — release history\n","readmeFilename":"README.md"}
![\"SCF](\"https://raw.githubusercontent.com/MarkAC007/mcp-server-scf/main/docs/assets/banner.png\")
\n \n