Does inspector support testing remote MCPs?

does this support testing remote mcps?

Yes. MCP Inspector supports testing remote MCP servers over HTTP-based transports:

• SSE (type: "sse", usually /sse)
• Streamable HTTP (type: "streamable-http", usually /mcp)
• Plus local stdio servers

The README describes the proxy as connecting the web UI to MCP servers via stdio, SSE, and streamable-http, and explicitly shows remote CLI examples.

###UI mode

Start the inspector:

npx @modelcontextprotocol/inspector

Then in the sidebar choose:

• SSE and enter your remote URL, e.g. https://example.com/sse
• Streamable HTTP and enter your remote URL, e.g. https://example.com/mcp

You can also prefill it:

http://localhost:6274/?transport=sse&serverUrl=https://example.com/sse
http://localhost:6274/?transport=streamable-http&serverUrl=https://example.com/mcp

###CLI mode

Examples from the repo:

# Remote server, default SSE
npx @modelcontextprotocol/inspector --cli https://my-mcp-server.example.com

# Remote Streamable HTTP
npx @modelcontextprotocol/inspector --cli https://my-mcp-server.example.com --transport http --method tools/list

# With custom headers
npx @modelcontextprotocol/inspector --cli https://my-mcp-server.example.com \
  --transport http \
  --method tools/list \
  --header "X-API-Key: your-api-key"

###Source-level confirmation

In server/src/index.ts, the proxy creates:

• SSEClientTransport(new URL(url), ...) for transportType === "sse"
• StreamableHTTPClientTransport(new URL(query.url), ...) for transportType === "streamable-http"

So yes, it’s designed to connect to arbitrary remote MCP server URLs, assuming the server exposes an MCP-compatible SSE or Streamable HTTP endpoint and any required auth/headers are provided.