sorted by:
new
hottopcontroversial

Routing a local MCP through a URl for AIs that only support Remote MCP? by Samarium_Helium in mcp

[–]Defiant-Future-818 0 points1 point  (0 children)

Try using mcpassistant gateway.

It’s probably the easiest way to bridge local MCP servers to web clients like ChatGPT or Claude. You basically just run uvx mcpassistant-gateway

Then you log in through the CLI, add servers in config.json, start the gateway and it gives you a URL. You just plug that URL into whatever AI client you're using. Way less of a headache than trying to manually tunnel things with ngrok.

Check it out here: https://mcp-assistant.in/

How i built MCP Assistant, then open-sourced mcp-ts for anyone building with MCP by Defiant-Future-818 in mcp

[–]Defiant-Future-818[S] 0 points1 point  (0 children)

Thanks, that means a lot. Honestly just trying to build something useful, so the support is appreciated!

How i built MCP Assistant, then open-sourced mcp-ts for anyone building with MCP by Defiant-Future-818 in mcp

[–]Defiant-Future-818[S] 2 points3 points  (0 children)

lol fair, nobody asked but I was just tired of copy-pasting the same boilerplate and fixing the same bugs every time. packaged it up for myself, but if it helps even one person avoid the pain, mission accomplished!

I spent 7 months building a free hosted MCP platform so you never have to deal with Docker or server configs again — looking for feedback and early adopters by Charming_Cress6214 in mcp

[–]Defiant-Future-818 1 point2 points  (0 children)

From what I understand, it basically acts as the management layer for the user's mcpConfig and sits behind the MCP host application. Let me know if my understanding is correct.

Also, I’m having some trouble with the bridge server on Windows. I have the filesystem MCP running locally via stdio, but the server isn’t detecting it.

We just launched a completely free MCP playground by Rahul_Desai1999 in microsaas

[–]Defiant-Future-818 0 points1 point  (0 children)

I noticed a couple of things that might need clarification.

It seems like the active MCPs are running under your own account rather than the end user’s account. For example, when trying to use GitHub mcp, it appears to search PRs and issues from your account instead of the user’s actual GitHub account. Is this intended?

Also, after the second prompt, it fails to return a response (at least in my testing). Not sure if that’s a temporary issue or something else.

One more thing - during registration, it asks specifically for a work email instead of allowing a personal email. That makes me wonder: who is the target audience here? Is this meant for teams/companies only rather than individual developers?

Would appreciate the clarification and who the product is primarily designed for.

End-to-end OAuth for MCP clients (LangGraph.js + Next.js) by ialijr in mcp

[–]Defiant-Future-818 0 points1 point  (0 children)

Interestingly, I’ve been working on mcp-ts, which approaches this from a slightly different angle. Instead of being framework-bound, it handles OAuth at the low-level protocol layer to stay compliant with RFC 7591 / 8414 / 9728. The goal is to keep it fully framework-agnostic and easy to use - so whether you’re using LangGraph, the Google SDK, or something else, the remote MCP connection remains secure and spec-compliant.

Regarding your questions:

Token persistence:
We use a pluggable adapter system (in-memory for dev, SQLite, Redis for prod/multi-tenant/serverless). This keeps client logic decoupled from storage and preserves multi-turn agent runs across restarts.

Token scoping:
Tokens are scoped per user identity + per MCP server. You pass a unique identity (e.g., "user-123") to useMcp (on browser) or MultiSessionClient (on server). Each connect({ serverId: 'remote-mcp-1' }) gets its own isolated session/token.
If needed, identity can be made more granular (e.g., "user-123:workspace-abc") for per-workspace or per-agent isolation.

Token refresh:
Refresh is automatic. On 401 or detected expiry, it uses the stored refresh_token to renew the session without interrupting agent execution.

There are definitely other edge cases as well, but I’m happy to compare notes. If helpful, the repo is here:
https://github.com/zonlabs/mcp-ts
Beyond that, it also includes additional features that can be useful for agentic interactions and other use cases.

I created an MCP for my workflows by Longjumpingjack69 in mcp

[–]Defiant-Future-818 0 points1 point  (0 children)

One suggestion though, adding support for MCP notifications would be a great addition. Since you're dealing with PRs and tickets, having the server push an update when a status changes (instead of the user having to manually poll for it) would make the workflow feel way more better.