Other MCP clients

Any client that supports remote MCP servers should work if it supports:

• the Streamable HTTP transport
• OAuth 2.1 sign-in with dynamic client registration

Add https://mcp.ybug.io/mcp as a remote server and follow the client's sign-in prompt. The server publishes its OAuth metadata at the standard /.well-known/ locations, so the client discovers everything else on its own.

If a client only supports local (stdio) servers, you can bridge it with mcp-remote:

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

Then check that it works.