The folks behind MCP protocol announced an official registry, currently in preview. MCP servers can be added to it now following the publishing guide.
Please publish to the official registry. I know at least Docker MCP Toolkit team is looking to add support for using the official registry once it’s in GA. I’d imagine most everyone is going to add support for it as well.
Thank you, we will do that!
There’s also updates coming to MCP spec in November to keep an eye on/start experimenting with. New features will be added that could make existing tools more useful or unlock new tools. Big one I remember is async support.
Saw an update on August 7, 2025 / ⛱️ Remote MCP Server, tons of small UI improvements and reminded me about this. Hadn’t been thinking about MCPs for a while, opting more for calling cli tools directly, because so many agents/clients have to load the entire MCP server schema into the context window at start. But they’re back on my radar now that Claude Code has new functionality to only search MCP tools as needed (see this GH issue for context). I’m assuming other agents/clients will implement similar functionality soon, so MCP is hot again imho 
All that to say, would still be great to see Fibery on MCP official registry. I still maintain that publishing of the MCP in more places is obviously good for existing customers, but is a great way to attract new customers, especially the ones you’ve identified as the focus for 2026 strategy - big 'ol nerds. 
Also related (thought I had brought it up somewhere but don’t see it in search) would be publishing it as a connector for Claude Desktop so it’s slightly easier for existing customers to use Fibery MCP in Claude Desktop (where they don’t have to configure it themselves), but more importantly (imho) have some free marketing for Fibery.
November MCP spec update also happened with that juicy async support (part of the larger “tasks” abstraction) and a whole bunch of other cool things that could supercharge the Fibery MCP.