Darwin integrations

Public, self-serve installation artifacts for Darwin's production MCP server:

https://mcp.darwin.so/mcp

The server dynamically advertises the canonical seven-tool Search → Act contract. These examples never copy a static tool schema into an agent framework; clients call MCP tools/list at runtime so tool metadata stays current.

Install now

• Generic remote MCP configuration

• VS Code workspace configuration

• Cursor configuration

• Client-by-client installation guide

• n8n MCP workflow template

• Gumloop reusable-node recipe

• Framework recipes

The separate Gemini CLI extension is installable with:

gemini extensions install https://github.com/darwin-studios/darwin-gemini-cli

Darwin is also active in the official MCP Registry as so.darwin/darwin.

Related MCP server: governed-rag-mcp

Verify the public contract

npm install
npm run smoke

npm run smoke initializes a real production MCP session, discovers tools dynamically, and asserts the seven canonical tool names. To also run one authenticated, read-only Search without putting a secret in source control, set DARWIN_ACCESS_TOKEN in the process environment.

Safety boundary

• Search is read-only. Action mutations are separate tools.

• A successful model turn is not proof that an Action completed; read the Action state.

• Never put Darwin tokens, provider credentials, payment data, or approval material in prompts, workflow exports, URLs, or committed configuration.

• Preserve capabilityRevision, actionId, and mutation requestId outside model prose.

• Close MCP clients in finally blocks and refresh tools when the contract changes.

Marketplace artifacts that require vendor review are intentionally not submitted from this repository. Darwin documentation labels those separately as Submission ready, Submitted, or Approved.

Release status