Claude MCP Server

Connect Claude to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Organize Claude Code memories, skills, MCP servers, and hooks via drag-and-drop dashboard. The claude mcp server is what makes that connection.

What the server does

CCO gives you cross-harness visibility. Claude Code has memories, skills, agents, hooks, slash commands, MCP servers, sessions, and context budget tracking. Codex CLI has AGENTS instructions, profiles, sessions, history, shell snapshots, TOML config, MCP servers, and skills. CCO scans each harness through its own adapter, shows the results in one dashboard, and lets you work across harness boundaries — preview files, run MCP security scans, back up harness state, and clean up misplaced config. Adding another harness is one adapter file.

Installation

The server ships on npm as @mcpware/cross-code-organizer, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by mcpware; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.