Skip to main content

agentvisor mcp

Interact with the MCP (Model Context Protocol) servers configured under mcp.servers in agentvisor.yaml.

Synopsis​

agentvisor mcp <subcommand> [options]

Subcommands​

SubcommandDescription
probeTest connectivity to a configured MCP server

probe​

Run a staged connectivity check against one configured MCP server, using the same config file the full runtime would load — without starting Temporal, the policy engine, or a sandbox. This turns an "edit your config, set an env var, boot the full runtime, and see what happens" round trip into one command.

agentvisor mcp probe <name> [options]

Arguments​

ArgumentDescription
<name>Server name, exactly as it appears under mcp.servers[].name in the loaded config

Options​

OptionDefaultDescription
--timeout10sMaximum time to wait for the probe to complete
--unsandboxedfalseProbe a stdio server as an unsandboxed host subprocess (development only)

What It Checks​

For an HTTP-based transport (sse, streamable_http), probe runs three stages:

  1. connect — a real TCP connection (and, for https://, a TLS handshake using the same trust configuration the real client would use)
  2. initialize — the MCP initialize handshake
  3. tools/list — lists the server's available tools

For a stdio transport, there is no CLI-side sandbox to run the server in safely. By default, probe refuses and instead prints the resolved command, arguments, and environment variable names (never values). Pass --unsandboxed to launch it as a real, unsandboxed host subprocess — the same posture sandbox=none uses, and appropriate only for local development.

A server configured with a principal-bound credential (principal_passthrough, token_exchange) has no principal available in a CLI context, so probe only runs the connect stage and reports the credential path as skipped, not failed.

Exit Codes​

CodeMeaning
0Server is reachable
1A required stage failed
2Usage or config error (unknown server name, stdio without --unsandboxed, credential resolution failure)

Example Output​

$ agentvisor mcp probe github --config agentvisor.yaml
Server github
Transport streamable_http
Endpoint https://api.githubcopilot.com/mcp/
TLS verify-full (system roots)

✓ connect 14ms
✓ initialize 52ms protocol 2025-06-18
✓ tools/list 9ms 26 tool(s)

✓ MCP server "github" is reachable

Examples​

# Probe an http-based server
agentvisor mcp probe github --config agentvisor.yaml

# Probe a stdio server, actually launching it (development only)
agentvisor mcp probe filesystem --unsandboxed

# Use a longer timeout for a slow upstream
agentvisor mcp probe internal-api --timeout 30s

See Also​

  • MCP Gateway — Configuring mcp.servers and credentials