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

# Build with AI

> AI tools and integrations for building on OMS with your IDE or coding assistant.

## Build on OMS with the open-money-stack skill

The fastest way to build a money-movement product on Polygon is the **open-money-stack** skill. It turns your AI coding assistant into a guided OMS implementation planner: it gets you authenticated, asks a few questions about what you are building (a neobank, remittance app, on-ramp, off-ramp, or payments app), and produces a plan wired to real OMS endpoints, marking what is callable today versus early access.

<Steps>
  <Step title="Install it">
    Add the hosted skill to your project with the skills CLI. It works with Claude Code, Cursor, VS Code, and other agent tools.

    ```bash theme={null}
    npx skills add https://docs.polygon.technology
    ```
  </Step>

  <Step title="Invoke it">
    Describe what you are building and your assistant uses the skill automatically:

    ```text theme={null}
    Build me a neobank on Polygon: users sign up, hold a USDC balance, top up with cash-in, and send to each other.
    ```

    Or call it explicitly by name (for example, `/open-money-stack` in Claude Code) to force it on a shorter prompt. You know it triggered when the assistant leads with authentication, asks the discovery questions, then lays out the customer to wallet to quote to transaction plan.
  </Step>
</Steps>

No design of your own? The skill points you to an [example neobank design system](https://docs.polygon.technology/example-design.md) you can adopt or restyle to your brand.

## Add docs context to your AI assistant

### Docs MCP Server

The PolygonDocs MCP Server gives your AI assistant direct, real-time access to these docs, no web search, no stale index. This is a **documentation lookup server**: it lets your assistant search across guides, API reference, and code examples. It does not execute code or connect to any Polygon services.

It works with Claude Code, Cursor, VS Code, and any MCP-compatible client.

<CodeGroup>
  ```bash Claude Code theme={null}
  claude mcp add --transport http "PolygonDocs" https://docs.polygon.technology/mcp
  ```

  ```json Cursor (mcp.json) theme={null}
  {
    "mcpServers": {
      "PolygonDocs": {
        "url": "https://docs.polygon.technology/mcp"
      }
    }
  }
  ```

  ```json VS Code (.vscode/mcp.json) theme={null}
  {
    "servers": {
      "PolygonDocs": {
        "type": "http",
        "url": "https://docs.polygon.technology/mcp"
      }
    }
  }
  ```
</CodeGroup>

Once connected, your assistant can search across guides, API reference, and code examples using the `search_mintlify` tool.

### llms.txt

For AI assistants that accept context files directly (Cursor rules, Claude project docs, system prompts), add the `llms.txt` URL as a reference. This file lists all documentation pages with descriptions so agents know where to find information.

```
https://docs.polygon.technology/llms.txt
```

In Cursor, add to `.cursorrules`:

```
Use https://docs.polygon.technology/llms.txt as a reference for all OMS developer documentation including embedded wallets, Trails API, Polygon CDK, and the Open Money Stack.
```

<Tip>
  `llms.txt` is a directory, it lists all pages so agents know where to look. `skill.md` is a capability summary, it tells agents what they can build and how. Use both together for the best results.
</Tip>