Where this server's MCP doors answer

GET

/api/v1/config/mcp-doors

const url = 'http://localhost:11044/api/v1/config/mcp-doors';
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-doors \
  --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'

The absolute URLs a client is configured with: url is the chat door (/mcp, with /mcp/chat as the same door spelled as one of a pair) and developerUrl is the code door for coding agents. FIELD PRESENCE IS CAPABILITY — developerUrl is ABSENT when this server serves no code door, so a client degrades to the chat door rather than to a 404. Same contract, and the same resolver, as the URLs the setup API states before it closes.

Authorizations

apiKeyAuth
basicAuth

Responses

200

The doors, as absolute URLs

*/*

Where a coding agent connects. The chat door is always there; the code door is present only on an appliance that enabled it, and its key is ABSENT rather than null when it is not.

object

chatAliasUrl

required

The same door under its alias, for a client pinned to the older path

string

developerUrl

The code door’s URL, present only where the code door is enabled. ABSENT, not null, so if (developerUrl) is right on every server that ever shipped

string

url

required

The chat door’s URL — a server fact no client can derive, because the published port is a host-side mapping

string