> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://docs.yodl.me/api/mcp` to find what you need.

# AI assistants

These docs are built to be read by machines as well as people. If you are integrating the SDK with an AI coding assistant, point it here rather than pasting snippets — everything below is available without an API key or an account.

## On every page

The **Ask AI** button at the bottom of each page opens the current page in ChatGPT or Claude, copies it as Markdown, links the raw Markdown, and — when you want the whole set — gives you the MCP server URL.

## Markdown routes

Append `.md` to any page URL to get its source rather than the rendered HTML:

```txt
https://docs.yodl.me/sdk/react-native/quickstart.md
```

Pages are also content-negotiated: a request without a browser `User-Agent` receives Markdown from the normal URL. So this returns Markdown, while your browser gets the rendered page:

```bash
curl https://docs.yodl.me/sdk/react-native
```

## llms.txt

Two files, both generated on every build:

| File | What it is |
| --- | --- |
| <a href="/llms.txt"><code>/llms.txt</code></a> | An index — every page with its title, path and one-line description. ~4 KB |
| <a href="/llms-full.txt"><code>/llms-full.txt</code></a> | The entire documentation concatenated into one file. ~80 KB |

Use the index to let a model choose what to read; use the full file when you want the whole corpus in context at once.

## MCP server

The docs are also served over the [Model Context Protocol](https://modelcontextprotocol.io), so an assistant can search and read them on demand instead of holding everything in context.

```txt
https://docs.yodl.me/api/mcp
```

```bash [Claude Code]
claude mcp add --transport http yodl-docs https://docs.yodl.me/api/mcp
```

```json [Client config]
{
  "mcpServers": {
    "yodl-docs": {
      "type": "http",
      "url": "https://docs.yodl.me/api/mcp"
    }
  }
}
```

Three tools are exposed:

| Tool | What it does |
| --- | --- |
| `list_pages` | Lists every documentation page with its title and path |
| `read_page` | Reads one page, by `pagePath` |
| `search_docs` | Searches the docs for a query string |

### What it can and cannot reach

:::note
This server exposes **documentation only**. It is read-only, needs no credentials, and can reach no account, wallet, payment or key material. There is nothing to scope and no token to leak.
:::

That is worth stating plainly, because many vendor MCP servers do the opposite — they connect an assistant to live project data, which is why their docs open with token-scoping and "don't point this at production" warnings. This one is closer to a search index over public pages.

It also does not serve the SDK's source code. The packages are published on npm ([`@yodlpay/react-native`](https://www.npmjs.com/package/@yodlpay/react-native), [`@yodlpay/react-native-eip-7702-provider`](https://www.npmjs.com/package/@yodlpay/react-native-eip-7702-provider)) and their types travel with them, which is the better source for an assistant writing integration code.

## One caveat

An assistant that has read these docs still guesses. The SDK's config example is type-checked against the real package on every build, so what you see compiles — but a generated integration is not. Check anything an assistant writes against the [API reference](/sdk/react-native/api), and let the compiler decide.