The agent's MCP server, tools and credential names
source is agent when the agent has saved settings (settings_revision is their revision) and release while it has none: settings then holds what the active release's card and policy pins say, which is what a session of that release does today. settings.allowed_tools are full mcp__<server>__<tool> names and empty when server is null; settings.credential_refs are credential names, never values. bound_credential_refs lists those of settings.credential_refs that have a live binding on the agent; a name without one blocks a new session until it is bound. available_servers lists, sorted and by id only, the servers a save may choose for this agent's workspace (never the built-in github, never a server's address or credentials). Saved with PUT …/mcp/settings, never as a release. Whoever manages the agent reads it, and so do the live members of its managing team.
Auth: cookie session only; no scope.
cookieSession__Host-werft_session<token>For the web console: the browser session cookie set by POST /v1/auth/login. It holds the scopes of the user's workspace role (owner: all; admin and member: all but sessions:recover). Requests other than GET must also send X-Requested-With: werft-web.
id*stringThe agent's id.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidThe settings and the revision that guards them.
application/json- response
source*string"agent""release"settings*settings_revision*|nullactive_release_id*|nullbound_credential_refs*array<>available_servers?array<>curl -X GET 'https://example.com/v1/agents/497f6eca-6276-4993-bfeb-53cbbbba6f08/mcp/settings'{ "source": "agent", "settings": { "server": "docs", "allowed_tools": [ "mcp__docs__read", "mcp__docs__search" ], "credential_refs": [ "docs-key" ] }, "settings_revision": 2, "active_release_id": "rel_example", "bound_credential_refs": [ "docs-key" ], "available_servers": [ "docs" ]}