MCP Gateway and Registry

Looks similar to MetaMCP https://github.com/metatool-ai/metamcp

Not sure which of these tools is currently the best but they are clearly needed.

I am testing MetaMCP to expose internal MCP servers to the cloud version of Claude, enabling me to use Home Assistant and some other internal services in verbal conversations with Claude app on the phone.

I think 3rd party MCP server use is available in other AI assistants as well but Claude is the only one who allows using them in Europe.

I can only wish that this would become a standard approach with any AI assistants, including the built in phone assistants like Siri, but Apple is so so far behind and always trying to squeeze every bit of money wherever they can, I doubt they will ever do that.

This approach enables better integrations with local services specific to different regions, and I would somewhat compare this to RSS feeds which were popular 15 years ago. Would be nice if most e-commerce sites would provide their own MCP servers for managing carts, placing and tracking orders, etc. I don't want to see a world where single monopoly grabs this market and makes things shit again (like it happened with social media), especially for those who live outside of USA.

> Caution: The current release (0.6.0) is considered alpha / early beta. It is not production-ready and should only be used for local development, testing, or experimentation. Features, APIs, and behaviors are subject to change without notice. Do not deploy in production environments without thorough security review, validation and additional security mechanisms. Many of the features required for secure, large-scale, or multi-tenant production deployments are still on the project roadmap - which is itself evolving.

IBM posting as if it were a solo open-source developer.

I built hyper-mcp[1] as side project with each MCP as a WASM plugin.

The idea is each plugin runs in their own wasm vm with limited network/file system access. Plugins are written in any language, as long as they can compile to WASM and publish to OCI registry (signed & verified with sigstore)

Recently, Microsoft released their own version of hyper-mcp named Wassete[2]

Ideally, I want to make it like a gateway with more security & governance features in this layer.

[1]: https://github.com/tuananh/hyper-mcp [2]: https://github.com/microsoft/wassette

If only IBM supported something more structured and sensible than the mess that is MCP: https://github.com/universal-tool-calling-protocol

These kind of gateways showcase that larger organizations will equip their employees with tools the same way employees are currently granted access to specific SaaS applications.

One of the bigger challenges we are currently observing is missing authorization for MCP servers.

We actually also just released a mcp-gateway[1] initially focusing on adding OAuth authorization to streamable HTTP MCP servers.

[1]: https://github.com/hyprmcp/mcp-gateway

I have built similar gateway but as a desktop application which runs locally and gives you a lot of control over enabled MCP tools and allows you to have a separate profiles for different combinations of MCP servers and credentials (e.g. profile with production API keys, sandbox keys and etc,.).

give it a try here: https://getaiko.app/downloads

So from what I gather this would be useful at a company level.

Everyone installs this gateway as their only "MCP", then at a central location we can add different MCP tools and everyone automatically gains access to them.

Ah nice an AI generated MCP gateway. I can't wait to see how many different agent/tool protocols we'll run through this year, and how many gateways. I just spin up oauth2proxy to handle authentication with istio gateway. Maybe I should be deploying piles of unknown code instead?

IBM pivoting to Ai, must be getting close to the top now.

I find the context forge quite nice from IBM. I used a few approaches they've implemented within my Ctxpack context management solution as well.

I think the agentic use cases aside, the client side of MCPs are still lacking quite a bit and would need to mature to be able to catch up to the spec. I feel a lot of use cases exist outside of fully automated agentic approaches, since we can't really rely on LLMs yet to produce at a human level.

The underserved cases rely a lot on prompt and resource management at the moment. Being able to iterate and share those across teams to provide easy starting points to delegate tasks is something I feel would be workable for the current iteration of AI assisted work, outside of pure software engineering.

Hopefully other clients join VS Code Copilot to allow more varied approaches than just simple tool calls here. I think Copilot's approach on prompt and resource management isn't quite the best approach either though. It is still early days for MCPs in general so i think we'll see a lot of experiments in this space.

Whats hilarious about this whole AI hype is that probably a million people are building the exact same software at the moment.

Many Gateways popping up now, im also doing my own gateway (https://mcp-boss.com/) but im starting to worry its hard to compete with Docker, Microsoft, now IBM...