Other MCP clients

Any tool that supports remote MCP servers can connect to Metal at:

https://mcp.metal.ai/mcp

The server uses streamable HTTP transport and OAuth authentication. Make sure an organization admin has enabled MCP first.

Clients that support remote MCP

Add the URL using the client’s standard MCP configuration. Most clients accept an entry like:

{
  "mcpServers": {
    "metal": {
      "url": "https://mcp.metal.ai/mcp"
    }
  }
}

On first use, the client opens a browser window to sign in with your Metal account.

Add a .vscode/mcp.json file to your workspace:

.vscode/mcp.json

{
  "servers": {
    "metal": {
      "type": "http",
      "url": "https://mcp.metal.ai/mcp"
    }
  }
}

Open the MCP view, start the metal server, and complete the browser sign-in.

Some clients can only launch a local command. Bridge to the hosted server with mcp-remote:

{
  "mcpServers": {
    "metal": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.metal.ai/mcp"]
    }
  }
}

mcp-remote handles the OAuth flow and forwards requests to the Metal MCP server.

Authentication loops or fails — confirm an admin enabled MCP under Settings → Organization → API & MCP Access.
Tools don’t appear — verify the URL includes the /mcp path and that your client supports remote (HTTP) MCP servers, or use the mcp-remote bridge above.

See the overview for the full tool list and shared troubleshooting.