cross-code-organizer — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Manage cross-harness MCP, skills, agent, session and configuration assets

What we know

Cross-Code Organizer (formerly Claude Code Organizer): cross-harness config dashboard for Claude Code, Codex CLI, MCP servers, skills, memories, agents, sessions, security scanning, context budget, and backups. Manage cross-harness MCP, skills, agent, session and configuration assets.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-06T12:36:53Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: modify tool configurations; back up or restore local settings. Complete write authority is not verified.
Local desktop/app configuration
Sensitive access: MCP credentials, IDE configurations and workspace files

May expose/edit sensitive local configuration and backup data; scope permission carefully.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

383 repository stars

Stars observed Oct 9, 2026.

Repository total for mcpware/cross-code-organizer.

All limitations / Review context

Has cross-code-organizer changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

May expose/edit sensitive local configuration and backup data; scope permission carefully.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Local desktop/app configuration
MCP credentials, IDE configurations and workspace files
Reviewed write actions: modify tool configurations; back up or restore local settings
Sensitive access: MCP credentials, IDE configurations and workspace files
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-06T12:36:53Z

Technical identity

github.com/mcpware/cross-code-organizer

Exact implementation source: https://github.com/mcpware/cross-code-organizer ↗
Reviewed resource type: Framework
Repository identity: mcpware/cross-code-organizer

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
mcpware/cross-code-organizer
Recorded repository material and project history.

Setup · Watchlist

Framework setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Cross-Code Organizer is a local configuration dashboard across coding harnesses; it is not itself a universal MCP server.
self hosted install or run · Publisher instructions
npx @mcpware/cross-code-organizer
Configure / authenticate
Publisher instructions
Cross-Code Organizer is a local multi-harness configuration manager, not a standalone stdio MCP service. Install/run dashboard per official README and protect existing Claude/Codex config; never treat scanning as authorization to change them.
Check connection
Suggested check
Read-only inspect of installed harness configurations before allowing changes.
Remove / uninstall / revoke
Suggested check
Stop CCO UI/CLI and remove its `/cco` skill from Claude Code skills directory if installed and no longer wanted; it is not a generic standalone upstream MCP server.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.

Official Documentation & Sources

What it does

Cross-Code Organizer (formerly Claude Code Organizer): cross-harness config dashboard for Claude Code, Codex CLI, MCP servers, skills, memories, agents, sessions, security scanning, context budget, and backups. Manage cross-harness MCP, skills, agent, session and configuration assets.

Capability: Developer Tools
Resource type: Framework
Best fit: Manage cross-harness MCP, skills, agent, session and configuration assets

Representative uses

Inspect MCP server configurations
Review agent and skill settings across clients
Back up local coding assistant settings
Manage cross-harness MCP, skills, agent, session and configuration assets

Limitations

May expose/edit sensitive local configuration and backup data; scope permission carefully.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local desktop/app configuration
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: MCP credentials, IDE configurations and workspace files
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: May expose/edit sensitive local configuration and backup data; scope permission carefully.

Access scope and cautions

Write actions: Not verified modify tool configurations back up or restore local settings
Sensitive access: MCP credentials, IDE configurations and workspace files
Risk level: high
Security notes: May expose/edit sensitive local configuration and backup data; scope permission carefully.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Inspect MCP server configurations; Review agent and skill settings across clients; Back up local coding assistant settings; Manage cross-harness MCP, skills, agent, session and configuration assets.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. Installation/authentication detail is incomplete; do not infer settings from package name. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Local desktop/app configuration

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: modify tool configurations; back up or restore local settings. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

MCP credentials, IDE configurations and workspace files Recorded sensitive-access context: MCP credentials, IDE configurations and workspace files.

What limitations and risks should I check before use?

May expose/edit sensitive local configuration and backup data; scope permission carefully. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.