Connect a Board

The kit needs an organization ID, a board ID, an API token, and an explicit base URL for board sync. This guide covers getting the credentials, where they’re stored, and how to change them later.

Get your credentials

Sign in at app.eventmodelers.ai/account
Generate an API token in your workspace settings — it is a UUID and is shown only once, so copy it immediately
Note your organization ID (from your organization settings) and the board ID (from the board’s URL)

Option 1: During installation

The installer asks for credentials interactively:

🔑 Enter your Eventmodelers credentials (press Enter to skip any field):

  Organization ID:
  Board ID:
  Token:

Paste each value, or press Enter to skip and connect later.

Option 2: With the `connect` skill

If you skipped credentials at install time, or need to change them later, use /connect inside Claude Code. The skill:

Checks for inline overrides (board=<uuid>, org=<uuid>, baseUrl=<url>) in the prompt that invoked it. A token is never accepted inline: the skills reference it as $EVENTMODELERS_TOKEN, which the loop sets from the kit config, so the value never appears in a prompt or transcript
Falls back to .eventmodelers/config.json for any value not overridden
Asks for missing credentials and uses https://api.eventmodelers.ai when baseUrl is missing
When it had to ask for missing values, writes them to .eventmodelers/config.json in the current working directory. If every value was already available (for example a complete config plus an inline board= override), it skips this step, so an inline override is not saved

The load-slice and update-slice-status skills call connect first, so you don’t have to wire credentials into them individually. The build-state-change, build-state-view and build-automation skills start with convention discovery and don’t call connect themselves.

Where credentials live

The installer, skills, and loop read configuration differently:

Reader	Configuration source
Installer	Reads `.eventmodelers/config.json` in the project root after you answer no to the existing-credentials question. If any of the three credential fields is missing, it prompts (including an optional API base URL) and writes all four fields to both config files; otherwise, it only completes them — adding a missing `baseUrl`, renaming `orgId` to `organizationId`, and filling the kit-local copy’s gaps from the root config.
`/connect` skill	Uses inline parameter > `.eventmodelers/config.json` in the current working directory > ask for missing credentials, with the skill’s default for `baseUrl`. It does not search both config locations.
Loop	Reads only `.build-kit/.eventmodelers/config.json`. A nonempty `BASE_URL` environment variable overrides that file’s `baseUrl`; `orgId` is read as a fallback for `organizationId`. There is no root-config fallback.

The loop requires organizationId, boardId, token, and baseUrl; missing values select local-only mode instead of board sync, and the loop prints which fields are missing. The installer writes baseUrl (the hosted platform URL unless you override it), so a fresh install connects without setting BASE_URL.

After installation or /connect, follow Check both config files, including the MCP URL check. /connect writes organizationId; the loop still reads orgId from older configs.

The installer keeps existing .gitignore rules and merges in .build-kit/ and .eventmodelers/. In a Git repository, it checks that the root token file is ignored and appends .eventmodelers/ again if needed. It warns if the file is still exposed. Follow Protect the token files after each installer run and confirm that the ignore check prints both paths before committing or launching the agent.

Verify the connection

npx github:Cratis/Eventmodelers-Build-Kit-CSharp status

Run this from the project root. It checks whether the kit, skills, and both config files exist, then prints saved values from the root config only. For example:

Connected to: https://api.eventmodelers.ai
Organization: <your-org-id>
Board:        <your-board-id>

Despite the Connected to: label, status makes no server request and does not verify credentials or inspect the kit-local config’s values. Follow Start the Claude loop to check board-sync startup and watch for platform errors.

Rotate or change credentials

Use /connect with an inline override to change the board for the skill session:

/connect board=<new-board-uuid>

Rotating credentials or changing boards requires updating both .eventmodelers/config.json and .build-kit/.eventmodelers/config.json. /connect does not synchronize the two files. Edit both (the installer only fills fields missing from the kit-local copy; it never replaces values already there), then repeat the MCP URL check. Repeat the token-file ignore check, then restart the loop.