This manual is for administrators responsible for deployment, service integration, user permissions, approvals, and operations. Employees connecting tools through Codex, Claude Code, or VS Code should read the user guide.
Start with a read-only call
Start MCPHub, initialize the administrator locally, sign in to the console, add a read-only service with its own credentials, test the connection, then publish tools and configure a test user. Complete login and client authorization. Once this works, enable writes gradually.
Install and start →Find your administration task
Prepare HTTPS, a database and an encryption key; initialize the administrator locally. Enterprise identity is optional.
02 · ServicesConnect and publish tools →Configure MCP backends or HTTP tool groups, define publication, and classify reads and writes.
03 · AccessConfigure users and groups →Create groups, assign group permissions, enable users and maintain memberships.
04 · GovernanceEnable writes safely →Set up independent approval, configuration governance, and audit archives. Verify execution results.
Recommended deployment order
- Install the gateway, choose local or remote administration, and retain the database and keys.
- Configure HTTPS and initialize the built-in administrator, then verify administrator and ordinary user login separately.
- Connect a service test its connection, and explicitly publish reviewed read-only tools through tool permissions.
- Grant group permissions and add users, enable client authorization, and share the user guide.
- Configure Vault when personal business accounts are needed, and approvals when write tools are needed.
- Verify a real ordinary-user call, revocation, and any required approval. Follow Operations to arrange health checks, backups, and diagnostics.
Assign three administration responsibilities
| Role | Main responsibility |
|---|---|
| Configuration administrator | Connect services, publish tools, configure access, and inspect diagnostics. |
| Write reviewer | Review the specific operation, target, arguments, and preview. Complete independent review as required by policy. |
| Security reviewer | Review configuration proposals; approve and apply changes when configuration approval is enabled. |
Documentation and acceptance checks
The configuration and operations chapters come directly from the repository's administrator manual, deployment guide, SSO, Vault, and configuration reference. Replace example domains and accounts with actual values. Passing validate, a health check, or template startup does not establish that identity, account, and approval integrations work. Check your actual environment using deployment verification.