MCP servers and skills can both be distributed to multiple apps, but their sync models differ:
- OcHub stores MCP JSON and writes it into enabled apps.
- The skills CLI installs skills, while per-app toggles on each card control distribution.
App support
| App | MCP | Skills |
|---|---|---|
| Claude Code | Supported | Supported |
| Claude Desktop | Not supported | Not supported |
| Codex | Supported | Supported |
| Grok Build | Supported | Not supported |
| OpenCode | Supported | Supported |
| OpenClaw | Not supported | Not supported |
| Hermes | Supported | Supported |
App toggles appear only where the capability is actually supported. OcHub does not manage native Claude Desktop or OpenClaw extensions through these pages.
Import existing MCP configuration
- Open MCP servers.
- Open the Import and sync icon at the top right, then select Import from app. An empty list also offers a direct import action.
- OcHub scans supported apps and adds only servers that are not already in its shared store.
- Review each row’s enabled-app summary and expand its arrow to change app toggles.
Importing does not delete unknown entries from an app automatically. A partial failure lists the entries that could not be imported.
Add an MCP server manually
Select Add, enter a name, optional description, and server JSON.
A stdio example:
{
"type": "stdio",
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem"]
}An SSE example:
{
"type": "sse",
"url": "https://example.com/sse"
}Choose at least one target app before saving. The JSON must be an object. Commands, arguments, environment variables, and related fields are converted to the format expected by each target tool.
Enable and sync MCP
- Expand the arrow at the end of a server row, then toggle apps on or off. Each toggle immediately updates that app’s configuration.
- To rewrite enabled servers, open Import and sync at the top right and select Sync to apps.
- Restart the target CLI so it reloads configuration.
- If the server is missing, check that the app is enabled, the config directory is correct, and the server transport is supported by the tool.
Edit, delete, and app toggles are in the expanded server details. Deletion requires confirmation and cannot be undone, so copy the JSON first if needed.
The server list shows a loading status while it is being read. If reading fails, select Retry. A failed refresh in the same workspace keeps the last loaded servers visible; it does not mean that your servers were deleted. If a remote workspace is disconnected, reconnect it before retrying.
Install a skill from the marketplace
- Open Skills → Discover and choose Marketplace search.
- Search for a use case such as
pdf,frontend, ortesting. - Select target apps under Install to.
- Select Install on the skill card.
- Return to Installed and confirm the skill and its source.
Discover skills from a repository
- Switch the Discover page to Repository browser.
- Enter
owner/repo,owner/repo@branch, or a full GitHub URL. - Add the repository, then select Refresh discovery.
- Install the skills you need from the results.
Disabling a repository removes it from discovery without uninstalling existing skills. Deleting the repository also does not uninstall those skills.
Update and distribute skills
- Check for updates compares local and remote versions.
- Update individually or use Update all.
- Per-app toggles control where the skill is synced.
- Directory opens the local install; Repository opens its remote source.
- Uninstalling asks the skills CLI to remove the skill from enabled apps.
Marketplace search and updates require network access. If the skills CLI is
unavailable, use Advanced features → CLI maintenance
to inspect its installation and PATH.
For Claude MCP and skills, Codex directories, and OpenCode or Hermes differences, see the Claude guide, Codex guide, OpenCode guide, and Hermes guide.

