Any other AI app

Connect apps that can only start a local MCP server, through mcp-remote.

Some AI apps only start MCP servers as programs on your computer (stdio) and can't reach one over the internet. mcp-remote, a small free program, bridges the two: the app starts it, and it talks to your panel.

You need Node.js 18 or later. Replace https://panel.example.com/mcp with your panel's MCP address.

API key

Most apps take a block like this in their MCP settings:

{
  "mcpServers": {
    "minimus": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://panel.example.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": { "AUTH_HEADER": "Bearer paste-your-key-here" }
    }
  }
}
  • AUTH_HEADER holds the whole value, Bearer and the key.
  • Keep Authorization:${AUTH_HEADER} without a space after the colon: some apps break arguments that contain spaces.

Sign in

Leave out the header:

{
  "mcpServers": {
    "minimus": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://panel.example.com/mcp"]
    }
  }
}

The first time the app starts it, mcp-remote opens your panel's sign-in page in your browser. Sign in, choose the scopes, and approve. It keeps the sign-in in ~/.mcp-auth. Signing in needs a browser on the same computer.

If it doesn't connect

  • Run the command yourself to see its messages: npx -y mcp-remote https://panel.example.com/mcp.
  • 401 in the messages: the key is wrong or revoked, or the sign-in expired — delete ~/.mcp-auth and sign in again.
  • Check that the panel's address opens in your browser from the same computer.