Skip to main content
Connect an MCP client to the authenticated Darwin server:
The server exposes six Action tools:
  • start_action
  • get_action
  • list_actions
  • update_action
  • approve_action
  • stop_action
get_action and list_actions require agent:read. Write tools require agent:write. Darwin derives the owner from authentication and rechecks every referenced AI, capability, Action, Turn, and approval.

​
Example flow

  1. Ask the client to search for a capability.
  2. Review the returned capability and revision.
  3. Ask it to use start_action with those exact identifiers.
  4. Use get_action until the status is terminal or needs attention.
  5. Use only the operation listed in availableActions for the next step.
When a connection or payment is required, compatible clients can receive Darwin’s first-party link through MCP URL elicitation. Opening the link does not complete the Action; get_action remains the universal recovery path. update_action can also submit bounded completion feedback or a safety_report. These are separate from ordinary messages and never imply approval. Action responses may contain a generic policyState; MCP never receives raw safety evidence, detector output, transcripts, or private reports. See the complete MCP setup and tool catalog.