1
Add the remote server
Add the remote server
Open your client’s MCP settings and add the endpoint above as a remote HTTP server. Name itDarwin if the client asks for a display name.Client menus change frequently. The server URL and Darwin tool contract do not.
2
Sign in and choose scopes
Sign in and choose scopes
Complete Darwin sign-in in the browser. Approve only the scopes the client needs:OAuth access is user-scoped and revocable. Provider connections and payment approvals remain separate from MCP authorization.
3
Verify the tool list
Verify the tool list
A full connection advertises one read-only Search tool and six focused Action tools.If the client shows a different tool set, reconnect before relying on it.
4
Try Search, then Act
Try Search, then Act
Ask:Search Darwin for OCR that supports handwriting and tables. Show me the provider, capability, match evidence, availability, and pricing before doing anything.After you select a result, ask:
Use that exact capability and revision to process this document. Keep the Action ID and stop if Darwin needs information, connection, payment, or approval.
Handle pauses correctly
A successful tool call can return nonterminal work. The client should renderstatus, actionRequired, availableActions, and any first-party webLink exactly as returned.
Troubleshooting
The client cannot discover Darwin tools
The client cannot discover Darwin tools
Confirm the endpoint is exactly
https://mcp.darwin.so/mcp, remove stale duplicate entries, then reconnect and complete OAuth again.Search works but Action tools fail
Search works but Action tools fail
The connection may only have
directory:read. Reauthorize with agent:write for Action reads and mutations.A task was interrupted
A task was interrupted
Use
list_actions or a stored actionId, then call get_action. Do not create replacement work until you know the existing Action state.