On this page
On this page
Get started
Manage company MCP plugins
Manage company MCP plugins
Administrators can publish remote MCP integrations under the OpenClaw publisher from Management → Plugins → Add MCP integration, or with clawhub-admin managed-mcp. The UI and CLI use the same authorized publication operation. The administrator must also have publishing access to the OpenClaw organization.
Each package contains a remote connection configuration, a short README, its icon, and license notices. OpenClaw publishes the wrapper; the named company operates the connected service. These packages do not contain provider implementations or local commands.
Publish and update
Supply a stable integration id, version, company, current category, brief description, public HTTPS endpoint, transport, authentication settings, and a PNG icon. Use company-provided artwork only when its terms permit this use. Record its attribution, rights or license label, official source URL, and license or brand-terms URL. The wrapper is MIT-licensed; a company icon keeps its separate rights. Original MIT icons remain supported.
--dry-run checks definition fields only. Icon decoding, endpoint compatibility, and security scans run during publication.
--icon reads a local PNG (at most 512KB) for a single definition. The JSON must include the icon's rights metadata; pngBase64 may be omitted when this option supplies it. Without --icon, put the PNG bytes in icon.pngBase64. For example:
This is the icon field, not a complete definition. Replace every example value with the reviewed asset's actual source and terms. Non-MIT icons require both URLs. Source URLs are provenance metadata, not live image links: publication stores the uploaded PNG in the versioned bundle, together with its terms in NOTICE. Neither the source URL nor the rights label proves permission; the operator must verify the provider's terms before publishing.
To edit a published integration, retrieve its latest submitted definition with get, update the fields, and increment version (for example, 1.0.0 to 1.0.1). Submit it through the same publish command. The admin HTTP API uses GET /api/v1/packages/-/managed-mcp/<id> and POST /api/v1/packages/-/managed-mcp with the complete updated definition. A changed icon cannot replace an existing version's bytes. The new release passes endpoint validation and normal security gates before becoming available; the previous version remains intact.
publish accepts one definition or an array of up to 200 definitions. A batch submits each entry through the same publication path. Stop on an error, correct the entry, and retry; normal immutable-version rules apply. Company integration lists are operational input to the CLI, maintained outside the application source tree and imported after the publishing code is deployed.
Use oauth with optional space-separated scopes, api-key with a header and an environment placeholder such as Bearer ${SERVICE_TOKEN}, or none. Never put credentials in the definition, endpoint, icon, or setup text. Keep endpoint paths, query restrictions, and HTTP/SSE transports as supplied by the service.
Publication checks the public endpoint and OAuth authorization/token discovery. Without an explicit client identity, the provider must advertise a public dynamic-registration endpoint (DCR).
For a provider using Client ID Metadata Documents (CIMD) instead, author connection.auth.clientMetadataUrl in the CLI definition alongside kind: "oauth" and any scope. Supply an actual hosted public HTTPS URL with a non-root path, no dot segments or fragment, and no credentials. The provider must advertise client_id_metadata_document_supported: true. Publication retrieves the document with the same bounded, public-DNS-pinned, no-redirect checks as discovery and requires an exact client_id URL match, a nonempty client_name, and nonempty usable redirect_uris. The document must not contain shared client secrets or shared-secret authentication methods; none and private_key_jwt are recognized, with key/runtime configuration remaining an operator responsibility. HTTPS web callbacks and native loopback HTTP callbacks are supported; callbacks are never fetched. The chosen CIMD identity and scope are retained in both generated manifests and the immutable managed definition; management UI edits preserve the CLI-authored identity.
Explicit CIMD configuration does not silently fall back to another DCR identity. The operator must host and maintain the real document and align its allowed callbacks and authentication method with the consuming OpenClaw runtime. Publication does not provision hosting, register a client, verify domain control, prove callback/runtime compatibility, establish account eligibility, complete consent, or execute an authenticated tool call.
Default native client identity
The public client document at https://clawhub.ai/oauth/clients/openclaw.json identifies OpenClaw as a public native client, without a shared secret. Its exact callback allowlist covers the CLI’s http://localhost:8989/oauth/callback and the default local Control UI at http://127.0.0.1:18789/oauth/provider/callback or http://localhost:18789/oauth/provider/callback. It does not grant consent or verify an account.
Custom ports, remote Gateway origins, and non-OpenClaw consumers need a separately hosted client document containing their actual callbacks. Do not add customer-specific Gateway URLs or arbitrary wildcard redirects to the shared native document. A Gateway operator can override a plugin-declared connection with a complete mcp.servers.<server-name> entry containing the same endpoint and its own oauth.clientMetadataUrl. That entry replaces the bundled connection; it is not a field-by-field merge. The plugin’s account status and browser sign-in follow the override when the server name and provider endpoint still match. A standalone plugin declaration is not resolved by openclaw mcp login; terminal login requires the explicit server entry.
Normal package validation and security gates apply, including to the OpenClaw publisher. A pending release is not installable. Scanning covers the published files and configuration; it does not certify the remote provider or its future tools.
Install and connect
The OpenClaw consumer must include the remote MCP loader fix. Until a release containing that fix is available, use a verified build containing it; older consumers may fail to start an agent session after enabling a remote MCP plugin.
Once available, users install the package through the normal OpenClaw plugin flow, enable it, and connect their account when required. API-key integrations require the named credential in a consumer that supports their environment placeholders. Account-level testing is separate from package validation.
OpenClaw's Control UI lists the plugin's MCP servers on its detail page. Follow the package's setup notes to connect the service.
Editing an icon or connection creates a new immutable version. Installed copies retain their existing files and settings until the user updates the plugin through OpenClaw's normal update flow. Publishing does not remotely force a reinstall on gateways. Unpublishing stops new availability through normal package policy; it does not uninstall existing copies.