Corezoid — Claude Code & Codex Plugin

A plugin for Claude Code and Codex that connects the Corezoid BPM 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.

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:

Requirements

• Claude Code or Codex installed
• Go 1.21+ available in PATH (the MCP server runs via go run, no build step needed)

  brew install golang        # macOS
  sudo apt install golang    # Ubuntu/Debian
  

• 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 install 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 install corezoid@corezoid

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

Updating

claude plugin update corezoid@corezoid   # Claude Code
codex plugin update corezoid@corezoid    # Codex

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 .env in your working directory and reused on every subsequent session. 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, set it in .env or export it before starting Claude Code or Codex:

export ACCESS_TOKEN=your_token_here

Configuration

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

Architecture

Claude Code / Codex
  └── corezoid MCP server (go run .)
        ├── Auth          login, logout
        ├── Workspace     list-workspaces, list-stages, list-projects
        ├── Processes     pull-process, pull-folder, push-process, lint-process
        │                 create-process, create-folder, create-alias, create-variable
        ├── Tasks         run-task, list-node-tasks, list-task-history
        │                 modify-task, delete-task
        └── Dashboards    create-dashboard, get-dashboard, add-chart,
                          modify-chart, get-chart, set-dashboard-layout

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 (CLAUDE_PLUGIN_ROOT for both Claude Code and Codex)
│   ├── .claude-plugin/
│   │   └── plugin.json          # Claude Code plugin manifest
│   ├── .codex-plugin/
│   │   └── plugin.json          # Codex plugin manifest
│   ├── .mcp.json                # MCP server configuration
│   ├── mcp-server/              # Go MCP server source
│   ├── skills/
│   │   ├── corezoid/                    # Universal assistant skill
│   │   ├── corezoid-init/               # Environment setup skill
│   │   ├── corezoid-create/             # Process creation skill
│   │   ├── corezoid-edit/               # Process editing skill
│   │   ├── corezoid-review/             # Process review skill
│   │   ├── corezoid-project-review/     # Project audit skill
│   │   ├── corezoid-dashboard-manager/  # Dashboard & chart management skill
│   │   └── corezoid-process-tech-writer/ # Process documentation skill
│   ├── 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 go run . 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

Note: If your Go installation is older than 1.24, the toolchain manager will try to download go1.24.0 from proxy.golang.org. In air-gapped environments set GOTOOLCHAIN=local and install Go 1.24+ manually. See Troubleshooting for details.

Links

• Corezoid
• Claude Code
• Changelog

License

MIT