MCP

VRPlatform MCP connects AI assistants, such as Codex or Claude, to your VRPlatform account.

After setup, your assistant can help with VRPlatform questions, look up teams you can access, read VRPlatform data when you ask it to, and make changes only when you explicitly confirm them.

What You Need

• an AI assistant that supports remote MCP servers
• a VRPlatform API token from Settings > API tokens
• the VRPlatform MCP URL

The full MCP URL includes your API token. Treat it like a password and do not share it in public chats, screenshots, or source control.

MCP URLs

Most users should use the production MCP URL:

https://mcp.vrplatform.app/

Use the staging MCP URL only when VRPlatform has asked you to test against staging:

https://staging.mcp.vrplatform.app/

Add your API token as api_key:

https://mcp.vrplatform.app/?api_key=<api-token>

The URL should end at /. Do not add /mcp unless VRPlatform gives you a URL that already includes it.

team_id is optional. Leave it out unless you want the assistant to start with one default team selected.

What It Can Do

• search VRPlatform documentation
• find teams by name
• read VRPlatform data for a selected team
• make changes after you explicitly confirm the action
• help clients discover available API endpoints and fields

Environments

The MCP host decides which VRPlatform environment the assistant uses:

Use an API token and team id from the same environment as the MCP host.

Read Next

• Setup
• Capabilities
• API Access
• Codex Setup
• Claude Setup
• Troubleshooting