Skip to content
Embabel Worlds

Set what a connected coding agent may do

PUT
/api/v1/config/mcp-mode
curl --request PUT \
  --url http://localhost:11044/api/v1/config/mcp-mode \
  --header 'Content-Type: application/json' \
  --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>' \
  --data '{ "mode": "ASSISTANT" }'

Body: {“mode”: “ASSISTANT”|“DEVELOPER”}. Persisted to config.yml and live IMMEDIATELY — the gate is read on every call, so an already-connected client simply retries.

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”

mode: ASSISTANT or DEVELOPER, trimmed and matched case-insensitively. Persisted to config.yml and read on every MCP call, so it applies without a reconnect; a missing or unrecognised mode answers 400

Media typeapplication/json

The mode a connected coding agent runs under

object
mode
required

ASSISTANT or DEVELOPER

string
Allowed values: ASSISTANT DEVELOPER

Responses

Section titled “Responses”

200

Section titled “200”

Mode updated

Media type*/*

The coding-agent mode was changed, and is live immediately

object
mode
required

The mode now in force

string

Example 

DEVELOPER
requiresReconnect
required

Always false: the gate is read on every call, so an already-connected client simply retries

boolean
status
required

Always updated

string

Example 

updated

400

Section titled “400”

The mode is not one the gate offers. An unrecognised mode is a client bug, so it is refused rather than silently resolved to a default

Media type*/*

A refusal from the world administration surface: what went wrong, and the word error so a client reading the body need not consult the status code

object
message
required

What was refused and why, written to be shown. Names the offending value where there is one — the unknown mode, the out-of-range threshold, the invalid cron expression

string
status
required

Always error. Present because the map this replaces carried it and a consumer may branch on it

string

Example 

error