Corezoid — Claude Code & Codex Plugin

A plugin for Claude Code and Codex that connects the Corezoid platform to Claude via MCP. Claude gets direct access to Corezoid processes and deep platform knowledge to create, edit, review, and deploy workflows through natural conversation.

Not just an MCP wrapper over the Corezoid API — an AI-Native management layer for the platform.

What it does

The plugin bundles a Go MCP server that exposes Corezoid operations as MCP tools and provides specialist skills that teach Claude the platform model and common workflows:

Design philosophy

This plugin is not simply an MCP wrapper over the Corezoid API. It is an attempt to build an AI-Native management layer — one that understands process structure, validation rules, and platform conventions deeply enough to create, audit, and deploy workflows through natural conversation.

Requirements

• Claude Code, Codex, or AWS Kiro installed
• A Corezoid account

Installation

Claude Code

From the GitHub marketplace:

claude plugin marketplace add corezoid/corezoid-ai-plugin
claude plugin install corezoid@corezoid

Or from a local clone:

git clone https://github.com/corezoid/corezoid-ai-plugin
claude plugin marketplace add ./corezoid-ai-plugin
claude plugin install corezoid@corezoid

Codex

From the GitHub marketplace:

codex plugin marketplace add corezoid/corezoid-ai-plugin
codex plugin add corezoid@corezoid

Or from a local clone:

git clone https://github.com/corezoid/corezoid-ai-plugin
codex plugin marketplace add ./corezoid-ai-plugin
codex plugin add corezoid@corezoid

No build step, no extra setup. The MCP server starts automatically on first use.

Telemetry: the plugin collects anonymous usage data (tool name, duration, error type, transport version) to improve reliability. No tokens, workspace IDs, or process content are ever sent. To opt out:

export COREZOID_ANALYTICS_DISABLED=1   # add to ~/.zshrc or ~/.bashrc to persist

AWS Kiro

git clone https://github.com/corezoid/corezoid-ai-plugin
cd corezoid-ai-plugin
sh plugins/corezoid/scripts/install-kiro.sh .

Open the workspace in Kiro — the corezoid MCP server, skills, and steering are picked up automatically. This also registers the plugin as a Kiro Power (~/.kiro/powers/installed/power-corezoid/), so it stays available in every Kiro workspace, not just this one — restart Kiro (or reload the window) to pick it up.

Updating

claude plugin update corezoid@corezoid   # Claude Code
codex plugin marketplace upgrade && codex plugin add corezoid@corezoid    # Codex

Codex has no plugin update subcommand — refresh the marketplace snapshot with codex plugin marketplace upgrade (upgrades all configured Git marketplaces; pass a name to target one) and re-run codex plugin add to install the refreshed version.

git pull && sh plugins/corezoid/scripts/install-kiro.sh .   # AWS Kiro

Restart Claude Code / Codex after updating to apply the new version.

Authentication

On the first Corezoid operation Claude detects that no token is present and runs the login tool automatically — your browser opens for OAuth2 sign-in and the session continues without interruption.

The token is saved to ~/.corezoid/credentials and reused on every subsequent session across all projects. When it expires, the login flow triggers again automatically.

You can also trigger login manually at any time:

log in to Corezoid

Static token (optional)

If you prefer to manage the token yourself, write it to ~/.corezoid/credentials:

ACCESS_TOKEN=your_token_here

Or export it as an environment variable before starting Claude Code or Codex:

export ACCESS_TOKEN=your_token_here

Configuration

Telemetry

The MCP server collects anonymous usage data (tool name, duration, error type, API hostname) to help improve the plugin. Tokens, workspace identifiers, process content, and personal data are never sent.

To opt out, set the environment variable before starting Claude Code:

export COREZOID_ANALYTICS_DISABLED=1

See SECURITY.md for the full list of collected fields.

Usage

Once installed, just talk to Claude naturally:

Pull my Corezoid workspace and show me what processes are in the Payments folder.

Create a process that calls any weather API, handles errors,
and sends the forecast back to the caller.

Create a folder named "Services" in Corezoid.

Edit the "payment" process — add retry logic on API timeout
with exponential backoff up to 3 attempts.

Edit process with id 1278273  — add retry logic
on API timeout with exponential backoff up to 3 attempts.

Review process ID 2778176 for dead nodes, missing error handlers,
and hardcoded values.

Review the process at 1278273_Business.folder/2778176_payment.conv.json
for dead nodes, missing error handlers, and hardcoded values.

Push the updated payment process to Corezoid and run a test task with
{"amount": 100, "currency": "USD"}.

Audit the entire Payments folder — list all processes, check for
validation errors, and summarize what each process does.

MCP Tools

Feedback

When the plugin does something unexpected, the corezoid-feedback skill guides you through collecting a description of the problem and sends it to the Corezoid team via the send-feedback MCP tool.

Privacy guarantees:

• Feedback is sent only after your explicit confirmation. Nothing is sent automatically.
• All fields are scanned for tokens, API keys, JWTs, and long hex secrets before transmission — any matches are replaced with [REDACTED].
• To disable feedback entirely (e.g. in corporate environments), set COREZOID_FEEDBACK_DISABLED=1.

Telemetry environment variables:

Architecture

Claude Code / Codex
  └── corezoid MCP server (prebuilt binary)
        ├── Auth          login, logout
        ├── Workspace     list-workspaces, list-stages, list-projects,
        │                 create-project, modify-project, delete-project, show-project,
        │                 deploy-stage, set-stage-immutable
        ├── Processes     pull-process, pull-folder, push-process, lint-process, layout-process
        │                 create-process, create-state-diagram, create-folder,
        │                 create-alias, create-variable,
        │                 list-variables, modify-variable, delete-variable,
        │                 show-folder, list-folders, modify-folder, delete-folder, delete-process
        ├── Tasks         run-task, list-node-tasks, list-task-history, get-node-stat,
        │                 modify-task, delete-task
        ├── Snapshots     create-snapshot, list-snapshots, delete-snapshot, get-snapshot
        ├── Dashboards    create-dashboard, get-dashboard, add-chart,
        │                 modify-chart, get-chart, set-dashboard-layout
        ├── Access        share-object, list-shares,
        │                 create-group, modify-group, delete-group, list-group-objects,
        │                 add-to-group, remove-from-group, list-groups,
        │                 create-api-key, modify-api-key, delete-api-key, list-api-keys,
        │                 find-principal, invite-user
        ├── Git context   git-pull-context, git-push-context,
        │                 read-context-file, update-context-file
        └── Feedback      send-feedback

Project structure

corezoid-ai-plugin/
├── .claude-plugin/
│   └── marketplace.json         # Claude Code marketplace listing (points to plugins/corezoid)
├── .agents/
│   └── plugins/
│       └── marketplace.json     # Codex marketplace listing (points to plugins/corezoid)
├── plugins/corezoid/            # Plugin root (skill path token; MCP launcher resolves it per host)
│   ├── .claude-plugin/
│   │   └── plugin.json          # Claude Code plugin manifest
│   ├── .codex-plugin/
│   │   └── plugin.json          # Codex plugin manifest
│   ├── .mcp.json                # MCP server configuration
│   ├── mcp-server/              # MCP server source
│   ├── skills/
│   │   ├── corezoid/                       # Universal assistant skill
│   │   ├── corezoid-init/                  # Environment setup skill
│   │   ├── corezoid-create/                # Process creation skill
│   │   ├── corezoid-edit/                  # Process editing skill
│   │   ├── corezoid-state-diagram-create/  # State diagram creation skill
│   │   ├── corezoid-state-diagram-edit/    # State diagram editing skill
│   │   ├── corezoid-review/                # Process review skill
│   │   ├── corezoid-project-review/        # Project audit skill
│   │   ├── corezoid-node-layout/           # Node auto-layout skill
│   │   ├── corezoid-dashboard-manager/     # Dashboard & chart management skill
│   │   ├── corezoid-process-tech-writer/   # Process documentation skill
│   │   ├── corezoid-process-optimizer/     # Process optimization skill
│   │   ├── corezoid-describe/              # Object description skill
│   │   ├── corezoid-alias-manager/         # Alias management skill
│   │   ├── corezoid-variable-manager/      # Environment variable management skill
│   │   ├── corezoid-api-connector/         # Corezoid public-API caller skill
│   │   ├── corezoid-gitcall/               # git_call custom-code skill
│   │   ├── corezoid-access/                # Sharing, groups, API keys skill
│   │   ├── corezoid-retro/                 # End-of-session retrospective skill
│   │   ├── corezoid-feedback/              # Bug / improvement reporting skill
│   │   ├── corezoid-git-context/           # `.git-context/` mirror sync skill
│   │   └── marketplace-publish-validation/ # Marketplace pre-publication checklist
│   ├── docs/                    # Node and process documentation
│   └── samples/                 # Example .conv.json processes

Debugging

The MCP server always writes debug output to /tmp/corezoid.log when running in MCP mode. View it with:

tail -f /tmp/corezoid.log

In CLI mode, enable verbose output with:

COREZOID_DEBUG=1 ./convctl pull-process process_id=123

Troubleshooting

See docs/Troubleshooting.md for solutions to common problems:

• Browser did not open during login
• Expired or missing ACCESS_TOKEN
• push-process validation errors
• MCP server startup failures
• Common Corezoid API error codes

Compatibility

Links

• Corezoid
• Claude Code
• Changelog

License

MIT