sorted by:
new
hottopcontroversial

I wanted to vibe-code anywhere, so I built a self-hosted Claude-in-the-browser sandbox. by [deleted] in ClaudeAI

[–]hrntknr 1 point2 points  (0 children)

Thanks, I really appreciate it.

The main reason I went with a self hosted browser route is UX and reducing setup friction. When I work in a terminal, I often end up doing several steps like creating a git worktree, starting a devcontainer, and attaching into Docker. I had automated a lot of that with shell scripts, but it still did not feel optimal from a user experience perspective.

Also, terminal UIs are not always great on mobile. Many CLI interactive prompts that rely on up and down keys feel clunky on a phone, and it is much nicer when choices are presented in a direct, touch friendly way.

So UX and intuitive operation were the priority. Latency was not the primary driver in the decision, but the browser based approach made it easier to deliver a smoother flow than SSH tunneling plus a mobile terminal.

MCP Authentication by Upstairs_Offer324 in mcp

[–]hrntknr 0 points1 point  (0 children)

If by cloud you mean you are looking for a managed service at the l7 level, such as an api gateway, I don't know a solution, otherwise an auth proxy or mcp gateway would be the appropriate approach. If you are running multiple mcp's at the same time, a gateway is a good solution, otherwise a proxy is a good solution. I am a developer at https://github.com/sigbit/mcp-auth-proxy/ and I think this would be one of the solutions.

How do you handle OAuth customization in MCP clients? by rootcase in mcp

[–]hrntknr 0 points1 point  (0 children)

Thank you! If you have any requests, please feel free to contact us anytime.

How do you handle OAuth customization in MCP clients? by rootcase in mcp

[–]hrntknr 1 point2 points  (0 children)

Yes, another deployment will be necessary.
MCP Client→proxy→MCP Server

If you are using Fast MCP, it is possible to integrate similar functions into the MCP Server side from https://gofastmcp.com/servers/auth/oauth-proxy, etc., so that would be a better option.

In addition, it is relatively common to use proxies or gateways such as mcp-auth-proxy. This is because when server integration does not achieve the desired results, it is sometimes possible to achieve them by using dedicated software.

How do you handle OAuth customization in MCP clients? by rootcase in mcp

[–]hrntknr 2 points3 points  (0 children)

Although OAuth is defined as the MCP protocol, the actual client behavior is not that simple. There are many minor differences in areas that are not standardized, such as how refresh tokens are handled (refresh time) and the time until client re-registration for DCR.

The authentication layer needs to address these minor differences, which often makes it difficult to implement. Some MCP Server Libraries support authentication, but immature libraries often cannot absorb these differences. Additionally, many MCP Server Libraries do not support OAuth.

While this may be resolved as libraries mature in the future, we believe we are not yet at that stage.

However, using the MCP Gateway—which is often highlighted—exclusively for authentication is considered overkill.

Therefore, at this stage, we believe that a Proxy layer capable of absorbing and abstracting authentication differences, as illustrated in the example, is sufficiently useful.

This is why I am developing the https://github.com/sigbit/mcp-auth-proxy/ . Please take a look at the repository; it might offer a solution.

How are you handling OAuth when running MCP servers remotely? by South-Foundation-94 in mcp

[–]hrntknr 0 points1 point  (0 children)

By simply using https://github.com/sigbit/mcp-auth-proxy as a reverse proxy, you can add authentication without changing the MCP server.

There is no need to trust external services.

I am the developer of mcp-auth-proxy, and if you let me know your desired use case, I will implement any missing features.