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

# MCP server

> Connect AI tools to the Vero OMS Docs MCP server

Use the Vero OMS Docs MCP server to let supported AI tools search the current documentation and retrieve API endpoint context.

## Server URL

Use this MCP server URL:

```text theme={null}
https://docs.vos.verolabs.co/mcp
```

## What the MCP server can access

The MCP server searches content indexed from Vero OMS Docs:

* REST API reference pages
* Streaming API documentation
* Vero OMS interface guides
* Integration documentation

It is a search/read MCP server. It is not a trading API and cannot place orders or call live APIs.

## Connect AI tools

### Codex

Run:

```bash theme={null}
codex mcp add vero-oms-docs --url https://docs.vos.verolabs.co/mcp
```

### Claude Code

Run:

```bash theme={null}
claude mcp add --transport http vero-oms-docs https://docs.vos.verolabs.co/mcp
```

### Cursor

Add the server to `mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "vero-oms-docs": {
      "url": "https://docs.vos.verolabs.co/mcp"
    }
  }
}
```

### VS Code

Add the server to `.vscode/mcp.json`:

```json theme={null}
{
  "servers": {
    "vero-oms-docs": {
      "type": "http",
      "url": "https://docs.vos.verolabs.co/mcp"
    }
  }
}
```

## Recommended prompt

```text theme={null}
Use the Vero OMS Docs MCP server to find the relevant endpoint or guide.
Use the OpenAPI spec as source of truth for method, path, parameters, auth, request body, and response schema.
Do not invent fields. If a live response conflicts with the spec, report the mismatch before implementing.
```