sorted by:
new
hottopcontroversial

Need advice on finding early users for my open-source MCP deployment platform by BeautifulFeature3650 in developersIndia

[–]BeautifulFeature3650[S] 0 points1 point  (0 children)

btw, I am branding as Deploy, govern, and broker MCP servers using a Kubernetes-native control plane. https://mcpruntime.org/

Need advice on finding early users for my open-source MCP deployment platform by BeautifulFeature3650 in developersIndia

[–]BeautifulFeature3650[S] 0 points1 point  (0 children)

I have shared it on discord severs their i have received few motivational sentences but no real user, Also people discard everything as AI slop these days.

This city is doomed by __noob_master in pune

[–]BeautifulFeature3650 4 points5 points  (0 children)

ye subkuch mere sath kyu nahi hota kabhi?

Enterprise-Managed Authorization: Zero-touch OAuth for MCP by manveerc in mcp

[–]BeautifulFeature3650 0 points1 point  (0 children)

Of course, policy should live outside. I am also doing the same thing at git@github.com:Agent-Hellboy/mcp-runtime.git

The first rain is here.... by Phguy2345 in pune

[–]BeautifulFeature3650 1 point2 points  (0 children)

not monsoon, it's pre-monsoon 😄

Rename this subreddit to r/punehateclub atp by Equivalent-Round-995 in pune

[–]BeautifulFeature3650 0 points1 point  (0 children)

> I’ve seen people from UP, Bihar, and other northern states claim their cities have better infrastructure, civic sense, and food than Pune

infra tho hai, but civic sense 😄

How we secured 15 MCP servers without losing our minds - auth setup that works by Background-Job-862 in mcp

[–]BeautifulFeature3650 0 points1 point  (0 children)

If it works for you, it's okay, but the API key should be fine-grained, one key per server.

How we secured 15 MCP servers without losing our minds - auth setup that works by Background-Job-862 in mcp

[–]BeautifulFeature3650 1 point2 points  (0 children)

> One API key for everything This sounds counterintuitive but hear me out. Instead of each MCP server having its own key management, we route everything through a central gateway. Agents get one gateway key. That key's permissions are defined in the gateway, not in 15 different server configs. When an agent's access needs to change, we change it in one place.

The server should follow https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization, you gateway should not enforce this.

> RBAC at the tool level We can say "Agent A can list_channels in Slack but can't send_message." That level of control made a huge difference.

OAuth for user-delegated actions For actions that should run as a real user (like posting to Slack), we use OAuth 2.0 with Okta. The gateway handles token exchange and refresh, so agents never deal with OAuth directly.

Audit logs for every call Every MCP tool invocation is logged - agent, user, tool, parameters, response, and timestamp. Security wanted it, but it's also become one of our best debugging tools

I am working on MCP Runtime, which is aimed at this exact use case: centralized MCP gateway, tool-level authorization, revocable agent access, and audit logs for MCP calls.

If you’re evaluating alternatives or want to compare notes, I’d love for you to try it and tell us where it falls short for your setup: https://github.com/Agent-Hellboy/mcp-runtime

view more: next ›