Welcome to mcprack’s documentation!

mcprack is a catalog and client-configuration portal for MCP (Model Context Protocol) servers. An administrator registers MCP servers once; every user picks the ones they need and gets a ready-to-use configuration for Claude Desktop, Claude Code, Cursor or VS Code. Clients never start a local process and never see a backend credential: they talk to a per-user relay URL on the mcprack server.

Version 1.7.0 adds two-factor authentication (required for administrators), fresh re-authentication for dangerous administrator actions, a tamper-evident audit mirror, command and URL policies, classified start-up diagnostics, mcprack user config verify and a secret-free Claude Code configuration format.

Key Features

• One catalog, many clients: generated configuration for Claude Desktop, Claude Code, Cursor and VS Code / GitHub Copilot.

• Per-user relay: stdio MCP servers run as per-user fastmcp processes on the mcprack host; network servers are relayed. Users receive one URL per server.

• Credentials stay on the server: shared credentials live in Vaultwarden or in an encrypted local store, and are injected when a request arrives. Users can override individual values for themselves.

• Access control: per-user server permissions, configuration templates, personal API tokens with scopes, optional MCP OAuth for clients such as Claude.

• Security for the open internet: LDAP or local accounts, two-factor authentication, login throttling, CSRF and session revocation, a command and URL destination policy, an audit trail with an HMAC-signed mirror.

• Operations: Debian packages, a systemd unit, an Apache vhost, Zabbix monitoring endpoint, OpenTelemetry, an Ansible collection.

Related projects

Project	Purpose
mcprack	The web application, REST API and mcprack command line tool
mcprack-client	Shared library of the sync tools
mcprack-sync-claude, -cursor, -vscode	Keep a client’s MCP configuration in sync with mcprack
mcprack-ansible-collection	vitexsoftware.mcprack Ansible collection
mcp-server-*	MCP servers that ship a mcprack-mcp-server-* companion package — see MCP servers with a mcprack companion

Getting Started

1. Quickstart — a running instance and a first server in ten minutes

2. Installation — installation, the files mcprack uses, upgrading

3. Connecting Claude Code — connect Claude Code

Contents

Getting Started

• What is mcprack?
• Quickstart
• Installation

Core Concepts

• Architecture
• The relay and its credentials
• Access control
• Credentials and secrets
• The audit trail

How-To Guides

• Registering an MCP server
• Granting access
• Connecting Claude Code
• Connecting other clients
• Enabling MCP OAuth
• Verifying a configuration
• Rotating the SECRET_KEY
• Monitoring

Security

• Security overview
• Authentication and sessions
• Two-factor authentication
• Fresh authentication for dangerous actions
• Policies for commands, URLs and installs
• The audit mirror
• Checklist for an internet-facing instance

Client Tools

• mcprack-client
• mcprack-sync-claude
• mcprack-sync-cursor
• mcprack-sync-vscode

Automation

• Ansible collection

MCP Servers with a Companion

• MCP servers with a mcprack companion
• Companion packages
• mcp-server-abraflexi
• mcp-server-datovka
• mcp-server-filesystem
• mcp-server-groupoffice
• mcp-server-mastodon
• mcp-server-semaphore
• mcp-server-subreg
• mcp-server-webdriver

Reference

• Configuration reference
• Command line reference
• REST API
• Client configuration formats
• Troubleshooting

Development

• Packaging an MCP server with a companion
• Contributing