Administering the platform
For platform admins and auditors of Open MCP Portal: people and teams, the catalog, access, records and operations.
Platform admins run an Open MCP Portal installation from the Admin side of the web app (the Workspace / Admin switch at the top of the sidebar). Platform auditors see every admin page, read-only.
Platform roles don't reach into teams' content: a platform admin uses a team's gateways only as a member of the team, uses a platform gateway only when granted, never changes a team's servers through the team's pages, and reads recorded call contents only through Admin › Calls, where every view is audited.
First run
The first platform admin, the first team and the settings to check.
Users and teams
Platform roles, suspending people, creating and archiving teams, and team overrides.
Catalog review
Approving servers and changed capabilities for the company catalog.
Publishing policy
Approval required or self-publish, and per-team overrides.
Internal networks
Which internal networks and hosts MCP servers may use.
Platform gateways
Gateways shared with teams, people and SSO groups.
Trusted clients
MCP clients that skip the consent screen.
Auth providers
OAuth apps for tools that act as the person calling.
Audit log
Every administrative change and sign-in.
Usage and calls
Calls through every gateway, and the usage dashboard.
Limits
Rate limits on gateways: defaults, ceilings and team overrides.
Retention
How long call records, contents, the audit log and usage are kept.
Payload capture
Redaction rules and patterns for recorded call contents.
Settings that must exist before the database is read (addresses, sign-in, keys) are environment variables; see Configuration.