OpenClaw MCP setup

Connect OpenClaw to SkilzVolt

Give OpenClaw OAuth access to your governed, shared skills vault. You do not need to create, paste, or share a connection key.

Which device or app are you using?

Choose the screen you use to access OpenClaw. The agent may run somewhere else.

Advanced details & governance

Workspace access and changes

The signed-in SkilzVolt user's live workspace memberships determine which workspaces are available. Skill writes create proposals and continue to follow each workspace's review policy.

How proposal reviews work

Writes create governed proposals and never overwrite approved content. Proposal review data is prepared asynchronously: an edit may briefly report a processing word diff, while a new skill has no earlier version to compare.

skills_proposal_status — Check the durable proposal status and word_diff_status.
skills_get_proposal_diff — Read the review package and word diff when its status is ready.

not_applicable — A new skill has no previous version to compare.
processing — The edit's persisted word diff is still being computed.
ready — The persisted word diff is available for review.
unavailable — The word diff could not be produced because processing failed.

Keep tools current

The MCP connection makes SkilzVolt tools and current user-authored workspace reference material available to OpenClaw. At bootstrap, skills_catalogue provides metadata only; it does not replace host, system, developer, or safety instructions, does not limit other available tools, and does not automatically install or synchronise skill content.

At connection bootstrap, call skills_catalogue to obtain authorised catalogue metadata without loading full skill content.

The OpenClaw bridge privately retains skill_id, workspace, current_version_id, and updated_at for each catalogue entry.

The model sees a compact line per entry in exactly this form: - name: description [SkilzVolt]

Full skill content is not part of the bootstrap catalogue; fetch it through skills_get when relevant.

skills_catalogue returns catalogue_revision, which covers both live authorisation and metadata. Pass that value as known_revision on a later refresh; refresh before relying on changed access or metadata.

Skills remain workspace-scoped. Same-name skills in different workspaces are distinct even when the compact model-visible lines are identical.

If catalogue bootstrap or refresh fails, report explicit degraded mode. Do not present cached metadata as current or silently substitute a local mirror.

Metadata-only bootstrap with dynamic MCP retrieval — OpenClaw can bootstrap an authorised compact catalogue, then read current approved organisation-specific skill content through skills_get only when it is needed.

The catalogue snapshot is short-lived and connection-bound, not a local mirror. SkilzVolt does not automatically install or synchronise local runtime copies of organisation-specific reference material. Full content must be retrieved through MCP when it is relevant.

If this client does not support tools/list_changed, call connection_diagnostic and compare the published tool contract version; use the shared connection/setup contract to refresh its tool catalogue only when the version is newer. Do not restart an otherwise healthy connection.