Skip to main content
MCP registry installation is not currently available in the workspace management console. The Add MCP server menu keeps Add from registry visible as a disabled Coming soon action so the future discovery path has a clear home, but it does not open a browser, navigate to another page, or call a registry API.
Do not configure a workspace registry or send users to a workspace catalog. The former workspace catalog route and registry-source settings have been removed from the management console.

​
Current MCP server sources

MCP servers currently enter a workspace in two ways:
  1. A workspace owner or administrator chooses Add MCP server → Connect by URL on an Agent or target and registers the remote Streamable HTTP endpoint directly.
  2. A platform administrator adds an MCP server under Workspace Defaults in the platform admin console. AcornOps materializes the default for eligible new workspaces; a workspace administrator then explicitly enables it and configures its authentication through the normal MCP setup.
Both paths create ordinary destination-owned MCP server installations. They use the same authentication, credential ownership, discovery, review, enablement, egress, and runtime rules. Platform defaults do not carry credentials into a workspace, and credentials are never copied between Agent and target installations.

​
Direct connection

Choose Connect by URL and enter the actual remote MCP Streamable HTTP endpoint, for example https://mcp.internal.example/mcp. The URL must be absolute HTTPS in production and cannot contain credentials or a fragment. The form does not accept a registry root, a /v0.1 registry API, server.json, a Git repository, a package, a container, or a stdio command. Configure private endpoint allow-lists and CA trust at deployment level before connecting an internal server. Newly discovered tools remain disabled until an owner or administrator reviews their capability and enables each exact server/tool pair. See MCP and tools for authentication, public-header, credential-ownership, review, and runtime behavior.

​
Platform-provided defaults

Platform administrators manage default MCP endpoint metadata in Platform admin console → Workspace Defaults → MCP servers. A default defines the display name, HTTPS endpoint, and where it is available. It does not contain a workspace credential. Workspace initialization snapshots the default definitions. Workspace administrators explicitly enable a starter to create an installation, then complete its normal authentication setup. That installation is workspace-owned and uses the same management and credential controls as a directly registered server. Later platform-default changes do not update the workspace’s saved starters or its installations.

​
Future registry experience

Registry discovery will move to a platform-administered experience in a future release. Until that experience is implemented and documented, the disabled workspace action is only a placeholder and registry import should not be treated as a supported production workflow. See Platform admin console for deployment-wide defaults and Configuration reference for remote MCP egress controls.