Help us improve
Share bugs, ideas, or general feedback.
From corezoid
Sets up a Corezoid working environment: authenticates via OAuth2, selects workspace/project/stage, and pulls the project folder. Invoke on first-time setup or when reconfiguring credentials.
npx claudepluginhub corezoid/corezoid-ai-plugin --plugin corezoidHow this skill is triggered — by the user, by Claude, or both
Slash command
/corezoid:corezoid-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a specialist in setting up the Corezoid working environment using the `corezoid` MCP server.
Assists with Corezoid BPM platform tasks: managing processes, nodes, JSON files, MCP tools, validation, and deployment via CLI.
Walks through Zapier MCP setup, authentication, and mode detection. Use for onboarding, reconnecting, or exploring what Zapier can do across 9,000+ apps.
Builds reusable Make API-call shells for SaaS retrieval (email, CRM, tickets) by discovering app modules, resolving connections, patching scenarios, and running as transport wrappers.
Share bugs, ideas, or general feedback.
You are a specialist in setting up the Corezoid working environment using the corezoid MCP server.
loginCall MCP tool login with no arguments. It will guide setup in one of two modes depending on whether the client supports MCP elicitation.
The login tool handles everything automatically in sequence:
ACCOUNT_URL~/.corezoid/credentialsWORKSPACE_ID to .envCOREZOID_STAGE_ID to .envWhen login returns "Setup complete", proceed to Step 2.
When elicitation is unavailable, drive the setup yourself using explicit tool calls. Follow this sequence exactly — never pick a workspace, project, or stage on behalf of the user. Always present the full list and wait for the user's explicit choice.
→ Ask the user: "What is your Corezoid Account URL? (e.g. https://account.corezoid.com)"
→ Call login(account_url=<value>)
The tool opens a browser for OAuth2 authentication and saves the token to ~/.corezoid/credentials.
→ Call list-workspaces
→ Show the full workspace list to the user. Ask the user to choose — do not select automatically.
→ Wait for the user's answer before proceeding.
→ Call list-projects(company_id=<workspace_id>) using the workspace the user chose.
→ Show the full project list to the user. Ask the user to choose — do not select automatically.
→ Wait for the user's answer before proceeding.
→ Call list-stages(project_id=<id>, company_id=<workspace_id>) using the project the user chose.
→ Show the full stage list to the user. Ask the user to choose — do not select automatically.
→ Wait for the user's answer before proceeding.
→ Call login(workspace_id=<workspace_id>, stage_id=<stage_id>)
When login returns "Setup complete", proceed to Step 2.
After login returns "Setup complete", call MCP tool pull-folder with:
folder_id: value of COREZOID_STAGE_ID (now set in .env)Do not proceed until the tool returns successfully.
If the user explicitly pastes values, write them to .env and skip the corresponding prompts:
COREZOID_API_URL=<value>
WORKSPACE_ID=<value>
COREZOID_STAGE_ID=<value>
Then call login — it will skip already-set values and only prompt for what's missing.
On private Corezoid installations, the OAuth2 browser flow may time out because localhost is not registered as an allowed redirect_uri (see issue #7). Symptom: browser opens the workspace UI instead of redirecting back.
Workaround — populate credentials manually before calling login:
ACCESS_TOKEN from the account UI at https://<host>/access_tokens (create a token manually)~/.corezoid/credentials:ACCESS_TOKEN=<token>
.env in COREZOID_WORK_DIR (the directory where Claude Code was opened):ACCOUNT_URL=https://<host>
COREZOID_API_URL=https://<host>
WORKSPACE_ID=<company_id>
COREZOID_STAGE_ID=<stage_id>
ps aux | grep "go run\|convctl" | grep -v grep | awk '{print $2}' | xargs kill
login — it will detect ACCESS_TOKEN in ~/.corezoid/credentials, skip OAuth, and complete setup.Credentials and project config are stored in two separate files:
| File | Contents | Notes |
|---|---|---|
~/.corezoid/credentials | ACCESS_TOKEN, ACCESS_TOKEN_EXPIRES_AT | User-level; shared across all projects; never in git |
<COREZOID_WORK_DIR>/.env | WORKSPACE_ID, COREZOID_STAGE_ID, API URLs | Project-level; one per workspace |
COREZOID_WORK_DIR is the directory where Claude Code was opened when the MCP server started (typically the project root). This is not the mcp-server/ source directory.
The MCP server loads ~/.corezoid/credentials first, then the project .env. A token in .env overrides the user-level one — useful for environments that manage credentials externally.
COREZOID_API_URL format⚠️ COREZOID_API_URL must be the base URL only — no path suffix:
✅ COREZOID_API_URL=https://your-corezoid-host.example.com
❌ COREZOID_API_URL=https://your-corezoid-host.example.com/api/2/json
The server appends /api/2/json or /api/2/download automatically.
| Variable | Stored in | Set during |
|---|---|---|
ACCOUNT_URL | project .env | login step 1 — API URL prompt |
COREZOID_API_URL | project .env | login step 2.5 — derived from account clients API |
ACCESS_TOKEN | ~/.corezoid/credentials | login step 2 — OAuth2 (or manually for on-prem) |
WORKSPACE_ID | project .env | login step 3 — workspace selection |
COREZOID_STAGE_ID | project .env | login step 4 — stage selection |
COREZOID_OAUTH_CLIENT_ID | project .env | pre-login (on-prem only) — OAuth2 client ID for deployments with a custom authorization server; cloud users do not need this |