Connect an AI Assistant Using VRTrust MCP
Learn how to connect an AI assistant such as Claude or Codex to your VRTrust account using the VRPlatform MCP server, so your assistant can look up data, answer product questions, and take action on your behalf.
Who This Applies To: VRTrust users who want to connect an AI assistant to their VRTrust account to access team data, search documentation, and run API requests.
Overview
VRTrust MCP is a server that allows compatible AI assistants to read and interact with your VRTrust data. Once connected, your assistant can search the VRTrust knowledge base, find teams you have access to, retrieve account data, and make changes after you explicitly confirm each action.
The recommended connection method uses OAuth — no API token required. An API token is only needed as a fallback if your AI client does not support OAuth.
Steps
Step 1: Add a Custom MCP Connection in Your AI Assistant
In Claude (or another compatible AI client), add a new Custom (remote) MCP connection and enter the following URL:
https://mcp.vrplatform.app/
That's it — no API key or token is needed in the URL when connecting via OAuth.
Claude-specific path: Settings → Integrations → Add custom integration → paste the URL above → Save.
Step 2: Authenticate via OAuth
When prompted, sign in with your VRTrust credentials to authorize the connection. OAuth handles authentication automatically — you will not need to copy or paste a token.
Step 3: Verify the Connection
Once connected, ask your assistant:
"Use VRTrust MCP to check the server status."
Your assistant should confirm the connection is active.
Fallback: API Token Method
If your AI client does not support OAuth, you can authenticate using an API token instead:
In VRTrust, go to Settings → API Tokens and create or copy a token.
Build your MCP URL:
https://mcp.vrplatform.app/?api_key=<your-api-token>
Optionally, append a default team ID:
https://mcp.vrplatform.app/?api_key=<your-api-token>&team_id=<your-team-id>
Paste this URL into your AI client's remote MCP server field.
⚠️ The full MCP URL contains your API token. Treat it like a password — do not share it in screenshots, public chats, or source control.
Important Considerations
OAuth is the preferred method. If OAuth is accepted by your client, an API token is not required.
For users with access to multiple teams: the MCP server does not lock the session to one team. You can scope individual requests to a different team during the conversation.
Your assistant will only make changes to your data when you explicitly confirm the action in the conversation.
Use tokens and URLs from the same environment (production vs. staging). Mixing them will cause connection errors.
Troubleshooting
My assistant says it cannot connect
Confirm you entered the URL exactly as shown:
https://mcp.vrplatform.app/If using the API token method, check that the token was copied without extra spaces and is still active in Settings → API Tokens.
My assistant cannot find my team
Ask your assistant to look up the team by name: "Find the team named [team name]."
My assistant says API access is not configured
Ask your assistant to run
vrt_server_statusand share the output to diagnose the issue.
Frequently Asked Questions
Do I need an API token to connect? No — if your AI client supports OAuth, you can connect using just the URL https://mcp.vrplatform.app/ and authenticate via OAuth. An API token is only needed as a fallback.
Do I need a team ID to connect? No. team_id is optional. If you leave it out, your assistant can look up teams by name during the conversation.
Can my assistant make changes to my data without me knowing? No. Your assistant will present any action and wait for your explicit confirmation before making changes.
What can my assistant do once connected? Your assistant can search VRTrust product documentation, find teams you have access to, read account data, and make changes after you confirm them.
Related Help Articles