What a connected coding agent may do

GET

/api/v1/config/mcp-mode

const url = 'http://localhost:11044/api/v1/config/mcp-mode';
const options = {method: 'GET', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url http://localhost:11044/api/v1/config/mcp-mode \
  --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'

ASSISTANT or DEVELOPER. The default is the deployment’s (Worlds declares DEVELOPER; Me leaves it ASSISTANT). Developer mode makes realm install and realm authoring guidance live, and makes MCP orientation lead with realms. Per user, which is per bearer token while a user holds one.

Authorizations

apiKeyAuth
basicAuth

Responses

200

The current mode

*/*

What a connected coding agent may do, and what it could be set to

object

mode

required

The mode in force for this user, resolved through the service rather than re-derived from config

string

Example

ASSISTANT

modes

required

Every mode this appliance offers, so a client need not hardcode the list

Array<string>

requiresReconnect

required

Always false. Nothing here needs a reconnect — the gate is read on every call, orientation re-reads the mode, and the realm tools export unconditionally. Kept as a field because clients already read it, and a client that stops telling people to reconnect is the point

boolean