# Build with AI assistants

> Give Claude, Cursor, ChatGPT or any AI assistant the MoreVoice docs: llms.txt, a Markdown version of every page, the OpenAPI description, and a docs MCP server.

Many developers now start an integration by asking an AI assistant. These docs are built for that: every page has a plain Markdown version, the whole site is available as one file, and a small MCP server lets an assistant search and read the docs while it helps you write code.

## Copy a page

Every page has a **Copy page** button next to its title. It copies the page as Markdown, ready to paste into a chat. The menu beside it opens the Markdown in your browser, or starts a new chat in Claude or ChatGPT that reads the page for you.

The Markdown version of any page is its address without the trailing slash, plus `.md`:

| Page | Markdown |
| --- | --- |
| `https://docs.morevoice.ai/get-started/quickstart/` | `https://docs.morevoice.ai/get-started/quickstart.md` |
| `https://docs.morevoice.ai/api/operations/calls_create/` | `https://docs.morevoice.ai/api/operations/calls_create.md` |
| `https://help.morevoice.ai/he/flows/` | `https://help.morevoice.ai/he/flows.md` |

Code samples come in all three languages, one after another, and notes and warnings become quotes, so nothing on the page is lost.

## The whole site in one file

The docs publish the [llms.txt](https://llmstxt.org) files assistants look for:

| File | What it holds |
| --- | --- |
| [`/llms.txt`](https://docs.morevoice.ai/llms.txt) | An index: what MoreVoice is, and links to the files below. |
| [`/llms-full.txt`](https://docs.morevoice.ai/llms-full.txt) | Every page of the developer docs in one Markdown file. |
| [`/llms-small.txt`](https://docs.morevoice.ai/llms-small.txt) | The same, without notes and tips, for smaller context windows. |
| [`/openapi.json`](https://docs.morevoice.ai/openapi.json) | The API's OpenAPI 3.1 description, with code samples for every operation. |

The help centre, which explains the web app, has its own: `https://help.morevoice.ai/llms.txt` and `https://help.morevoice.ai/llms-full.txt` (in Hebrew; every article has an English version under `/en/`).

## The docs MCP server

`https://docs.morevoice.ai/mcp` is a [Model Context Protocol](https://modelcontextprotocol.io) server. Connect it to your assistant, and it can search the developer docs and the help centre, then read the pages it needs, instead of guessing from what it learned in training. It is free, needs no account or key, and only reads public docs.

**Claude Code**

```sh
claude mcp add --transport http morevoice-docs https://docs.morevoice.ai/mcp
```

**Claude**

In Claude (the web app or Claude Desktop), open **Settings › Connectors**, choose **Add custom connector**, name it `MoreVoice Docs` and enter `https://docs.morevoice.ai/mcp`.

**Cursor**

Add it to `.cursor/mcp.json` in your project (or `~/.cursor/mcp.json` for every project):

```json title=".cursor/mcp.json"
{
  "mcpServers": {
    "morevoice-docs": { "url": "https://docs.morevoice.ai/mcp" }
  }
}
```

**VS Code**

Add it to `.vscode/mcp.json` in your workspace:

```json title=".vscode/mcp.json"
{
  "servers": {
    "morevoice-docs": { "type": "http", "url": "https://docs.morevoice.ai/mcp" }
  }
}
```

Any other client that speaks MCP over Streamable HTTP works the same way: the URL is all it needs.

### Tools

| Tool | What it does |
| --- | --- |
| `search_docs` | Searches both sites and returns the five best pages with their URLs. Arguments: `query` (English or Hebrew), and optionally `lang` (`en` or `he`; by default the language of the query), `site` (`docs` for the developer docs, `help` for the help centre) and `limit` (1–10). |
| `get_page` | Returns one page as Markdown. Argument: `url`, a page URL from `search_docs`. |

Then ask as you normally would, for example: "Using the MoreVoice docs, write a Node.js script that calls a test number and prints the transcript."

> **Docs, not your account**
>
> The docs MCP server only reads the public documentation. It can't see or change anything in your MoreVoice organisation, and it never needs an API key.

## Tips

- **Point the assistant at a test key.** Ask it to read `MOREVOICE_API_KEY` from the environment and to start with a test key (`mv_test_sk_…`): see [test mode](https://docs.morevoice.ai/get-started/test-mode/). Test calls are simulated and never billed.
- **Let it check the API description.** Assistants are good at reading [`/openapi.json`](https://docs.morevoice.ai/openapi.json): field names, required parameters and error codes come straight from it.
- **Verify what matters.** Read the code before you run it against live calls, especially anything that dials numbers or changes compliance settings.
