Skip to main content
Connect Darwin as a remote MCP server when your Claude account supports custom MCP connections. Use the same URL for all clients:

​
Connect and try it

Add Darwin in your client’s connector or plugin settings and review the tools and requested permissions. Complete Darwin sign-in in the browser when a protected operation requires it. Never paste credentials, API keys or payment details into an assistant conversation. Try this request:
Darwin advertises exactly six tools:

​
Continue and approve

Keep the returned conversationId, actRequestId, thread IDs and retry keys. Preserve any guest continuation token privately. Read progress before retrying an uncertain request. A new request ID should not be used to repeat an uncertain write. Choose an agent and review the scope before starting work. Account access and consequential controls require the appropriate Darwin OAuth grant. Authentication and checkout use the returned secure hosted flows. Connecting an account, showing a view, or sending ordinary text does not approve work or payment. An accepted request or pending checkout is not completed work or settlement. Live Search and provider execution retain their release gates.

​
Existing installations

The endpoint, OAuth identity, scopes and saved state remain unchanged. Refresh the tools or reconnect and start a new chat if Claude retains an older catalog. Old names remain callable for cached sessions but are not advertised for new work. Directory listings may cache reviewed schemas and require their own update or review process; deploying this catalog does not prove directory approval. Embedded UI depends on host support. When a view is unavailable, Darwin still returns readable text and structured results. Chat attachments are sent only when the host explicitly includes supported context in the tool call. See the MCP quickstart for examples and security for account and authorization boundaries. If your client cannot connect securely, use Navigator.
Last modified on November 1, 2026