VRPlatformVRPlatform

Other Clients

Configure any Streamable HTTP MCP client

Other Clients

Use Streamable HTTP transport and point the client at the full MCP URL, including query parameters:

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

Add &team_id=<team-id> only if you want a default team for the session.

The API token comes from Settings > API tokens in VRPlatform. The server does not currently use bearer-token MCP auth. The token is read from the api_key query parameter.

The workers.dev endpoint remains available if you need a Cloudflare fallback:

https://vrt-mcp.vrplatform.workers.dev/?api_key=<api-token>

Required Client Support

The client should support:

  • Streamable HTTP MCP transport
  • MCP tools
  • MCP resources, if you want API discovery from vrt://api/*
  • MCP prompts, if you want to use vrt-trust-accounting-help

Some clients support tools but not resources or prompts. In those clients, use the tools that are visible and keep API-shape discovery in a client that can read MCP resources.

If the client supports tool deny lists, disable vrt_api_mutation for read-only workflows.

On this page