Other Clients

Use Streamable HTTP transport and point the client at the MCP URL:

https://mcp.vrplatform.app/

Add ?team_id=<team-id> only if you want a default team for the session. If the client asks for a server name, use vrplatform.

OAuth is the primary authentication method. The server advertises OAuth protected-resource metadata and accepts the bearer token from the MCP client.

If a client cannot complete OAuth, use an API token from Settings > API tokens as an api_key query parameter:

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

Required Client Support

The client should support:

• Streamable HTTP MCP transport
• OAuth protected-resource metadata and bearer-token auth, or API-token fallback
• MCP tools
• MCP resources, if you want API discovery from vrplatform://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.

Recommended Safety

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