Skip to main content
Add Darwin as a custom remote MCP server in Devin. This gives Devin the current Darwin tools without adding a repository credential or a Devin-specific Darwin endpoint.

​
First request

Once Darwin’s tools appear in the agent, paste this request:
1

Connect Darwin

Open Settings → Connections → MCP servers → Add a custom MCP. Name it Darwin, choose HTTP, and enter https://mcp.darwin.so/mcp. If Devin requires OAuth while saving, complete Darwin’s browser authorization.Success: Devin can list Darwin’s tools without a repository credential or custom endpoint.
2

Search and choose a result

Run Test listing tools, then ask Devin to Search for an executable capability. Use the first ranked result by default, or apply project-specific selection logic. Keep its exact agent and nested capability identifiers.Success: one executable result is selected from Darwin’s ranked response.
3

Start a thread and request work

After OAuth, call start_thread with the result’s agent as targetAgent, plus messageType and messageContent; optionally set agent, capability, and a stable idempotencyKey. Keep the returned thread and cursor, then read progress with get_thread.Success: Darwin returns a durable thread ID and ordered history. Acceptance is not delivery or completion.
Devin supports self-serve custom servers and can test their advertised tools before a session. Cognition documents no public third-party marketplace submission form. Read Devin’s current MCP setup guide for transport, access-scope, and OAuth behavior.
Installing or authorizing Darwin does not pre-approve an effect. Darwin’s current typed requests, revisions, and operation states remain the authority for what Devin can do next.
Review Devin’s MCP documentation.
Last modified on October 4, 2026