Skip to main content

Connecting an Agent

The server is reachable over HTTP at a single endpoint:

https://mcp.virtualmetric.com/mcp

The transport is MCP over HTTP. Clients that default to the stdio transport — the one used for MCP servers running as a local subprocess — must be told to use HTTP explicitly; a client left on stdio will attempt to launch a local binary and fail with a missing-command error rather than a network error.

Credentials​

The server needs no sign-in, API key or token. A tool works only on the arguments that its call sends, such as a pipeline and sample logs.

Claude Code​

Register the server with claude mcp add, passing the transport and the URL:

claude mcp add --transport http vmetric https://mcp.virtualmetric.com/mcp

The server is registered under the name vmetric, which is how its tools are namespaced in the agent's tool list.

Other MCP Clients​

Any MCP client that supports the HTTP transport connects to the same URL. The shape of the configuration differs by client, but it always holds the same two values: the transport and the URL.

The generic form, as a JSON server entry...

{
  "vmetric": {
    "type": "http",
    "url": "https://mcp.virtualmetric.com/mcp"
  }
}

Verifying the Connection​

Ask the agent to list the available processors. The call reaches list_processors, which requires no arguments and no pipeline, so it exercises the full path, from the transport to the engine, without depending on anything you have authored. A returned catalog confirms the connection; anything else is one of the failures below.

Troubleshooting​

SymptomCause
The client tries to launch a local commandThe transport was left at its stdio default — set it to HTTP explicitly
404 Not FoundThe path was omitted. The endpoint is /mcp; the bare host serves only a redirect to this documentation
405 Method Not AllowedThe client issued a GET. The endpoint accepts POST only
The first call after a quiet period is slowExpected cold-start behavior — see Limits and Safety

For the request-size cap and the one-request-per-call rule, both of which surface as parse errors rather than connection failures, see Limits and Safety.