Configuring Your MCP Tool

You need to configure your MCP tool to access Virtualize as an MCP server by providing it the endpoint <BASE_URL>/soavirt/mcp. You can do this a couple ways.

Adding it to Your Configuration

You can add the endpoint to your configuration. For example:

{
  "servers": {
    "soatest": {
      "type": "http",
      "url": "http://localhost:9080/soavirt/mcp",
      "headers": {"Authorization": "Basic <credentials>"}
    }
  }
}

{
  "servers": {
    "soatest": {
      "type": "http",
      "url": "http://localhost:9080/soavirt/mcp",
      "headers": {"Authorization": "Bearer <token>"}
    }
  }
}

Your authorization header can be either "Authorization": "Basic" or "Authorization": "Bearer", as appropriate for your Virtualize server. When using Bearer authorization, you will need to provide the token. When using Basic authorization, encode your username and password like you would for any other HTTP basic authorization header. For example, if the Virtualize server credentials are username user and password pass, you would configure as "headers": {"Authorization": "Basic dXNlcjpwYXNz"}. The account you are using must have at least Provision access to use MCP tools.

Adding it with VS Code

You can add the MCP server endpoint using the VS Code CLI. For example:

Linux

code --add-mcp '{"name":"soatest","type":"http","url":"http://localhost:9080/soavirt/mcp"}'

Windows

"C:\Program Files\Microsoft VS Code\bin\code" --add-mcp {\"name\":\"soatest\",\"type\":\"http\",\"url\":\"http://localhost:9080/soavirt/mcp\"}