# Quick start

If you use Claude Code, add the docs MCP server with one command:

Ask

```bash
claude mcp add --transport http moov-docs https://docs.moov.io/mcp
```

For other tools, see the [setup instructions](https://docs.moov.io/guides/developer-tools/mcp-ai/docs-mcp/#set-up-your-ide) below.

# What is MCP?

The [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) is an open standard that lets AI coding tools connect to external data sources. When your IDE supports MCP, it can call tools provided by an MCP server on your behalf — searching documentation, fetching pages, or listing available sections without leaving the editor.

The Moov **docs MCP server** is a read-only documentation search tool. It does not call the Moov API or make changes to your account. For live API operations like creating accounts and transfers, use the [Moov TypeScript SDK MCP server](https://docs.moov.io/guides/developer-tools/mcp-ai/mcp/).

# Available tools

| Tool | Description |
| --- | --- |
| `search_moov_docs` | Full-text search across all Moov documentation pages |
| `get_moov_doc` | Retrieve the full content of a specific documentation page by path |
| `list_moov_sections` | List all available documentation sections and their paths |

# Set up your IDE

Ask

```bash
claude mcp add --transport http moov-docs https://docs.moov.io/mcp
```

Ask

Create a `.cursor/mcp.json` file in your project root:

```json
{
  "mcpServers": {
    "moov-docs": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://docs.moov.io/mcp"]
    }
  }
}
```

Ask

Add to your Windsurf MCP configuration (`~/.codeium/windsurf/mcp_config.json`):

```json
{
  "mcpServers": {
    "moov-docs": {
      "serverUrl": "https://docs.moov.io/mcp"
    }
  }
}
```

Ask

Add to your VS Code settings (`.vscode/mcp.json`):

```json
{
  "servers": {
    "moov-docs": {
      "type": "http",
      "url": "https://docs.moov.io/mcp"
    }
  }
}
```

Ask

Add to your Zed settings (`~/.zed/settings.json`):

```json
{
  "context_servers": {
    "moov-docs": {
      "url": "https://docs.moov.io/mcp"
    }
  }
}
```

Ask

Add to your Cline MCP settings (`~/.cline/data/settings/cline_mcp_settings.json`):

```json
{
  "mcpServers": {
    "moov-docs": {
      "type": "http",
      "url": "https://docs.moov.io/mcp"
    }
  }
}
```

Ask

```bash
gemini mcp add --transport http moov-docs https://docs.moov.io/mcp
```

Or add to your settings (`~/.gemini/settings.json`):

```json
{
  "mcpServers": {
    "moov-docs": {
      "httpUrl": "https://docs.moov.io/mcp"
    }
  }
}
```

# Example prompts

Once the MCP server is installed, try prompts like these with your AI assistant:

- Create a Moov account and request `send-funds.ach` capability
- Show me how to initiate an ACH transfer with the Go SDK
- Generate a scoped OAuth token for linking a bank account to an existing account
- What payment methods are available for instant payouts?
- How do I verify a bank account with micro-deposits?
- What capabilities do I need for card issuing?

The docs MCP server searches documentation — it does not call the Moov API. Your [API keys](https://docs.moov.io/guides/get-started/api-keys/) are not needed for MCP setup. For live API operations, see the [Moov MCP server](https://docs.moov.io/guides/developer-tools/mcp-ai/mcp/).

# LLM context files

These plain-text files follow the [llms.txt convention](https://llmstxt.org/) for making documentation available to AI tools.

**[llms.txt](https://docs.moov.io/llms.txt)** — A structured overview of Moov's documentation with links to every section. Some AI tools automatically fetch `llms.txt` from a site's root when given a domain. You can also paste it into a conversation to give your AI assistant a map of what's available.

**[llms-full.txt](https://docs.moov.io/llms-full.txt)** — The complete content of every documentation page concatenated into a single file. Use this when you want to load all of Moov's docs into a context window at once, or feed it into a custom RAG pipeline or agent.

**When to use which:**

- Use the **MCP server** when your AI tool supports it — it searches on demand and only returns relevant pages, keeping context small.
- Use **llms-full.txt** when your tool doesn't support MCP, or you want to front-load all docs into a long-context model (e.g. paste URL into Claude, Gemini, or use `@docs` in Cursor).
- Use **llms.txt** when you want your AI tool to understand the structure and decide which pages to fetch individually.

# Docs MCP vs Moov MCP

| Server | What it does | Needs API keys? |
| --- | --- | --- |
| **Docs MCP** (`docs.moov.io/mcp`) | Searches and reads Moov documentation | No |
| **[Moov MCP](https://docs.moov.io/guides/developer-tools/mcp-ai/mcp/)** (`moov TypeScript SDK`) | Calls the Moov API — creates accounts, transfers, etc. | Yes |

The docs MCP server searches documentation. For live API operations like creating accounts and transfers, use the [Moov TypeScript SDK MCP server](https://docs.moov.io/guides/developer-tools/mcp-ai/mcp/).