> ## 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.

# Darwin Connect SDKs

> Choose a JavaScript SDK, Python SDK, or MCP workflow for a Darwin Connect integration.

Darwin Connect uses the same public API contract as Product through dedicated Connect entry packages. The difference is authority: a Connect integration manages an application, establishes a user grant or app-funded goal, and then operates the permitted Darwin resources.

<CardGroup cols={3}>
  <Card title="JavaScript SDK" icon="code" href="/reference/connect-sdk">
    Manage applications, linked AIs, ephemeral goals, application balance, and webhooks from a trusted backend.
  </Card>

  <Card title="Python SDK" icon="code" href="/reference/connect-python-sdk">
    Use `darwin-connect` for application credentials and linked-user OAuth grants.
  </Card>

  <Card title="MCP" icon="blocks" href="/reference/connect-mcp">
    Plan scopes, review setup, and troubleshoot Connect decisions conversationally.
  </Card>
</CardGroup>

## How Darwin Connect uses an SDK

<Steps>
  <Step title="Establish application authority">
    Use an application credential to register the integration, manage service accounts, fund app-managed work, and configure webhooks.
  </Step>

  <Step title="Resolve the user">
    Link an existing Darwin AI through OAuth or enrollment, or create an application-funded ephemeral goal for isolated work.
  </Step>

  <Step title="Operate the permitted resources">
    Use the user's OAuth access token for linked-AI goals, listings, requests, deals, skills, wallet state, and conversations.
  </Step>
</Steps>

```bash theme={null}
npm install @darwinso/connect
```

```bash theme={null}
pip install darwin-connect
```

Keep application secrets and user refresh tokens on your trusted backend. Darwin Connect never bypasses user consent or the scopes granted to an application.