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

# Get Started

> Choose your path: no-code automation, direct API, or AI agent via MCP or CLI.

# Get Started

The Unified API under `/api/v2` is the recommended default for new focused data integrations. Pick the path that matches how you're connecting.

## Choose your path

<CardGroup cols={3}>
  <Card title="Make.com, n8n or similar" icon="workflow" href="/documentation/v2/get-started#no-code-automation">
    Use your DumplingAI API key as a connection credential in any no-code or automation platform.
  </Card>

  <Card title="Building my own app" icon="code" href="/documentation/v2/get-started#direct-api">
    Call the Unified API directly from your code. Create an API key and use Workbench to explore capabilities.
  </Card>

  <Card title="Claude, Codex, Cursor or similar" icon="bot" href="/documentation/v2/get-started#ai-agents">
    Connect your AI agent through `/mcp/v2` or the DumplingAI CLI. No API key needed — sign in with OAuth.
  </Card>
</CardGroup>

***

## No-code automation

1. Create an API key in the [DumplingAI dashboard](https://app.dumplingai.com/api-keys)
2. Paste it as a connection credential in Make.com, n8n, Zapier, or any HTTP-based automation tool
3. Follow the platform-specific setup guides:
   * [Make.com setup](https://app.dumplingai.com/integrations/make-dot-com)
   * [n8n templates](https://n8n.io/creators/yang/)

***

## Direct API

1. Create an API key in the [DumplingAI dashboard](https://app.dumplingai.com/api-keys)
2. Call the Unified API run endpoint with your key:

```bash theme={null}
curl -X POST https://app.dumplingai.com/api/v2/run \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "type": "capability",
    "id": "search_news",
    "input": {
      "query": "latest AI infrastructure news",
      "dateRange": "pastWeek"
    }
  }'
```

3. Use [Workbench](https://app.dumplingai.com/workbench) to inspect inputs, outputs, and available capabilities.

See the [Unified API](/unified-api-platform) page for a full overview of the capability and provider-endpoint model.

***

## AI agents

No API key required — connect through MCP or the CLI and sign in with OAuth.

### MCP

Add this server URL to your AI client:

```text theme={null}
https://mcp.dumplingai.com/mcp/v2
```

Client-specific one-liners:

| Client      | Command                                                                        |
| ----------- | ------------------------------------------------------------------------------ |
| Claude Code | `claude mcp add dumplingai --transport http https://mcp.dumplingai.com/mcp/v2` |
| Codex       | `codex mcp add dumplingai --url https://mcp.dumplingai.com/mcp/v2`             |
| Cursor      | Use Cursor's remote MCP server option with `https://mcp.dumplingai.com/mcp/v2` |
| ChatGPT     | Add `https://mcp.dumplingai.com/mcp/v2` as your MCP server or connector URL    |

See the full [MCP Server guide](/mcp-server) for screenshots and OAuth flow details.

### CLI

Run capabilities, search the catalog, and inspect details from your terminal:

```bash theme={null}
npx dumplingai
```

See the [CLI guide](/cli) for all available commands.

***

## Next steps

<CardGroup cols={2}>
  <Card title="MCP Server" icon="plug" href="/mcp-server">
    Client-specific MCP setup for Claude, Codex, Cursor, ChatGPT, and more
  </Card>

  <Card title="CLI" icon="terminal" href="/cli">
    Run capabilities and explore the catalog from your terminal
  </Card>

  <Card title="Unified API" icon="book" href="/unified-api-platform">
    Learn the v2 capability and provider-endpoint model
  </Card>

  <Card title="API Reference" icon="book" href="/api-reference/v2/introduction">
    Browse the transport endpoints and request model for `/api/v2`
  </Card>
</CardGroup>

## Looking for direct endpoints?

Use [the Direct Endpoints Get Started page](/documentation/v1/get-started) when you specifically want legacy request shapes, the Direct Endpoint Playground, or the current Make.com module flow.