MCP connection requirements
To connect to Virtana MCP, each client needs three basic settings: the transport protocol, the server endpoint, and authentication details. The transport protocol is always streaming HTTP. The endpoint URL and authentication method vary by product.
Required settings
The following settings are required for an MCP connection:
Parameter | What it Means | Value or Format | Notes |
|---|---|---|---|
Transport Protocol | The method used to establish the MCP connection. | streaming-http | This is the only supported transport protocol. |
Server Endpoint | The URL of the MCP server you want to reach. | Product-specific URL | Use the endpoint listed for your Virtana product. |
Authentication | The credentials used to authorize requests. | HTTP headers | The header format varies by product. |
Product connection details
The following table shows the connection details for each Virtana product:
Product | Endpoint URL Format | Authentication Method |
|---|---|---|
Infrastructure Observability (IO) | https://<io_server>/api/sdk/mcp/ | Bearer token in the HTTP Authorization header |
Global View (GV) | https://<your-platform-url>/mcp | OAuth token in the HTTP Authorization header |
Connection setup summary
For Infrastructure Observability (IO)
Endpoint: https://<io_server>/api/sdk/mcp/
Note
Trailing slash required. The URL must end with a /. Omitting it will cause the connection to fail.
Transport: streaming-http
Auth Type: Bearer token
Header Format: Authorization: Bearer <your-token>
For Global View (GV)
Endpoint: https://<your-platform-url>/mcp
Transport: streaming-http
Auth Type: OAuth token
Header Format: Authorization: Bearer <your-oauth-token>