# VOOI\_ULTRA:MCP

## Overview

VOOI MCP provides an agent-facing interface for working with VOOI Perps API through MCP-compatible clients.

Instead of integrating separately with each supported perpetual trading venue, an AI agent can connect to VOOI MCP and access VOOI Perps functionality through a single tool layer.

VOOI MCP can be used to interact with supported trading venues through tools exposed to compatible AI clients, IDEs, and coding agents.

## What is VOOI MCP?

VOOI MCP is a Model Context Protocol server for VOOI Perps API.

It allows compatible AI agents to access VOOI trading tools through the MCP standard. The MCP client handles the agent interface, while VOOI MCP connects the agent to VOOI Perps API.

VOOI MCP is designed for workflows such as:

* checking open positions;
* reviewing balances and account data;
* working with perpetual trading venues through one interface;
* using VOOI Perps tools from coding agents or AI-enabled IDEs.

## Supported clients

VOOI MCP can be connected to several MCP-compatible clients:

* **Codex CLI**\
  Terminal-based coding agent. Uses HTTP MCP configuration.
* **Claude Desktop**\
  Desktop AI assistant. Requires a local bridge because Claude Desktop uses stdio MCP configuration.
* **Claude Code**\
  Terminal-based coding agent. Supports HTTP MCP configuration.
* **Cursor**\
  AI-enabled IDE. Uses MCP configuration in mcp.json.

## Before you start

Before connecting VOOI MCP, make sure you have:

* a supported MCP client installed;
* a VOOI API token;
* access to the environment where the MCP client runs;
* basic familiarity with editing config files or running CLI commands.

You can generate a VOOI API token from the VOOI Ultra user token page:

<https://ultra.vooi.io/api-tokens>

Store the token securely. Do not paste it into public chats, screenshots, logs, or shared config files.

## MCP endpoint

Use the following VOOI MCP endpoint when configuring your client:

```
https://vooi-api-app.fly.dev/mcp
```

VOOI MCP uses Bearer token authentication.

Most clients should read the token from an environment variable instead of storing the raw token directly in the configuration file.

Recommended environment variable name: `VOOI_API_TOKEN`

## Basic connection flow

The exact setup depends on the client, but the general flow is the same.

1. Install or open the MCP-compatible client.
2. Generate a VOOI API token.
3. Store the token in an environment variable.
4. Add the VOOI MCP server to the client configuration.
5. Restart the client if required.
6. Verify that the `vooi-perps` server is connected.
7. Use the exposed VOOI tools from the AI agent.

## Security recommendations

Keep your VOOI API token private.

**Do not:**

* hard-code the token in shared config files;
* commit config files containing raw tokens to git;
* paste tokens into AI chats or support messages;
* share screenshots that include tokens.

Use environment variables where supported.

If a token is exposed, revoke it and generate a new one.

## Next steps

* VOOI MCP: [Connect Codex CLI](/vooi-ultra-v3/vooi_ultra-mcp/connect-codex-cli.md)
* VOOI MCP: [Connect Claude Desktop](/vooi-ultra-v3/vooi_ultra-mcp/connect-claude-desktop.md)
* VOOI MCP: [Connect Claude Code](/vooi-ultra-v3/vooi_ultra-mcp/connect-claude-code.md)
* VOOI MCP: [Connect Cursor](/vooi-ultra-v3/vooi_ultra-mcp/connect-cursor.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vooi.io/vooi-ultra-v3/vooi_ultra-mcp.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.