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

# Build with AI

> Connect Flynet to Claude Code, Cursor, and other AI coding agents — live docs, an agent skill, and editor rules.

# Build with AI

Flynet works with AI coding agents through four installable surfaces — live docs, a direct-call MCP, an agent skill, and editor rules. Use one or all; they compose.

## Pick a surface

<CardGroup cols={2}>
  <Card title="Docs MCP" icon="server" href="/build-with-ai/mcp-servers">
    Your agent searches the live Flynet docs in real time — no copy-paste, always current. Works in any MCP-aware client.

    ```bash theme={null}
    claude mcp add --transport http flynet-docs https://docs.flynet.org/mcp
    ```
  </Card>

  <Card title="API MCP" icon="bolt" href="/build-with-ai/mcp-servers">
    Your agent calls Flynet directly — list restaurants, read a member's wallets — through 9 read-only tools. Runs locally; your credentials stay on your machine.

    ```bash theme={null}
    npx -y @flynetdev/mcp
    ```
  </Card>

  <Card title="Agent skill" icon="wand-magic-sparkles" href="/build-with-ai/agent-skills">
    Teaches Claude Code the two-credential auth model, the `@flynetdev/core` and `@flynetdev/react` surfaces, and the rules that trip up first integrations.
  </Card>

  <Card title="Cursor rules" icon="file-pen" href="/build-with-ai/agent-skills">
    The same guardrails as project rules for Cursor, so generated code uses the right header for each route and composes the real components.
  </Card>
</CardGroup>

## Compare by use case

| You want to…                                                                          | Use                                    |
| ------------------------------------------------------------------------------------- | -------------------------------------- |
| Let your agent look up an endpoint, field, or error while it codes                    | **Docs MCP**                           |
| Let your agent run real Flynet calls — fetch a restaurant, read wallets — as it works | **API MCP**                            |
| Make Claude Code understand the whole Flynet surface before it starts                 | **Agent skill**                        |
| Keep Cursor's generations consistent with Flynet's auth and components                | **Cursor rules**                       |
| Ground a one-off question without installing anything                                 | **Docs MCP** (or the `llms.txt` below) |

## Supported clients

| Client         | Docs MCP | API MCP | Agent skill | Cursor rules |
| -------------- | -------- | ------- | ----------- | ------------ |
| Claude Code    | Yes      | Yes     | Yes         | —            |
| Cursor         | Yes      | Yes     | —           | Yes          |
| Claude Desktop | Yes      | Yes     | Yes         | —            |
| VS Code (MCP)  | Yes      | Yes     | —           | —            |

## Use them together

<Note>
  These aren't alternatives. The skill front-loads the approach, the Docs MCP grounds specifics at the moment the agent needs them, and the API MCP runs the calls. Most setups pair the skill with the Docs MCP.
</Note>

## No client? Use `llms.txt`

Every Flynet docs page is available as plain markdown for any model:

* [`llms.txt`](https://docs.flynet.org/llms.txt) — an index of the docs, optimized for LLM context.
* [`llms-full.txt`](https://docs.flynet.org/llms-full.txt) — the full docs as one file.
* Append `.md` to any docs URL to get its markdown source.

## Next

<CardGroup cols={2}>
  <Card title="Full walkthrough: ship with Claude →" icon="rocket" href="/build-with-ai/walkthrough">
    All of it in one pass — wire up Claude, build on the SDK, handle secrets safely, deploy on Vercel.
  </Card>

  <Card title="Set up the MCP servers →" icon="server" href="/build-with-ai/mcp-servers" />
</CardGroup>
