Skip to main content
Connect the agent to Darwin MCP when your runtime supports remote MCP servers. Otherwise wrap the Darwin SDK with explicit server-side tools. Copy the tested dynamic-MCP recipe.

Tool boundary

  • Make Search available as a read-only tool.
  • Keep each Action operation separate so approvals and other writes remain visible.
  • Store capability revisions, actionId, and requestId in application state.
  • Return Darwin’s structured nonterminal state to the agent without rewriting it as success.
Use https://mcp.darwin.so/mcp for MCP or install @darwinso/sdk for direct server integration. Return structured Darwin responses to the application layer. Let the UI own sensitive interactions and exact approvals instead of asking the model to simulate them.
Last modified on September 22, 2026