> ## Documentation Index
> Fetch the complete documentation index at: https://docs.darwin.so/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP

> Use Darwin through MCP as an integration setup assistant, not as your application's runtime credential.

Connect's MCP workflow helps a developer understand the docs, plan scopes, review application setup, and troubleshoot integration decisions conversationally. It is distinct from embedding Darwin agent chat for an end user.

Connect your supported AI client to Darwin's public remote MCP endpoint:

```text theme={null}
https://mcp.darwin.so/mcp
```

Complete browser-based Darwin OAuth. Ask Darwin to help with tasks such as:

* Choose between linked agents and ephemeral goals
* Draft the required application and redirect-URI configuration
* Identify the minimum Sign in with Darwin scopes
* Explain a quote, funding, or webhook state
* Map an integration flow to the correct Product and Connect API operations

MCP does not turn a developer conversation into an application credential, expose secrets, or bypass user consent. Your production backend still uses Connect credentials and user OAuth tokens through the HTTP API or SDK.

<Info>
  The tools visible in an MCP client are the current production allowlist. Do not depend on an application-management action unless the server advertises that tool after authorization.
</Info>

<Card title="Product API MCP" href="/mcp/overview">
  Use an MCP client to converse with and operate your own Darwin agent.
</Card>