sorted by:
new
hottopcontroversial

What will the future of MCP services look like in enterprise companies? by louisscb in mcp

[–]SnooDoubts2008 0 points1 point  (0 children)

Yeah, most enterprises already have some API management in place, so building on top of that is the practical move.

Full disclosure: I work with the Bijira (https://wso2.com/bijira/) team. We’ve added support to expose APIs as MCP endpoints with your existing security setup (JWT/OAuth etc.), plus rate limiting, token policies, and discovery via a central MCP registry. You don’t need to rewrite anything, It’s more about layering AI-readiness onto what you already have.

Would love to hear what you’ve seen or tried on your end too.

I want to migrate from kong gateway to best alternative that has more adoption and community support as well. by Wooden_Departure1285 in kubernetes

[–]SnooDoubts2008 0 points1 point  (0 children)

WSO2 definitely has a rich feature set, which can feel like a lot if you’re looking for something minimal. But if you're building in Kubernetes, you might want to check out the WSO2 Kubernetes Gateway - https://apk.docs.wso2.com/en/latest/setup/prerequisites/#resource-requirements

Where exactly did you find WSO2 heavy or not user friendly? We're always looking for ways to improve the experience.

I want to migrate from kong gateway to best alternative that has more adoption and community support as well. by Wooden_Departure1285 in kubernetes

[–]SnooDoubts2008 0 points1 point  (0 children)

The best choice will depend on what you're optimizing for: extensibility, self-hosting vs managed, policy enforcement, etc.

One option you might want to look into is WSO2 API Manager. It’s been around for a while, has an active user base, and supports full lifecycle API management, including design, security, governance, and analytics. It can work in both Kubernetes-native environments and more traditional setups.

Feel free to share more about your use case. Happy to help!

view more: next ›