# \[DONE\] Publish MCP server to official MCP Registry **URL:** \ **Category:** Ideas & Features\ **Tags:** mcp\ **Created:** [October 13, 2025, 8:07pm UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805 "2025-10-13T20:07:10Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\ **Post date:** [October 13, 2025, 8:07pm UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/1 "2025-10-13T20:07:10Z")
The folks behind MCP protocol [announced](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/) an official registry, currently in preview. MCP servers can be added to it now following the [publishing guide](https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/publishing/publish-server.md). 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. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [October 14, 2025, 8:23am UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/2 "2025-10-14T08:23:39Z")
Thank you, we will do that! ---
**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\ **Post date:** [October 14, 2025, 12:44pm UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/3 "2025-10-14T12:44:20Z")
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. ---
**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\ **Post date:** [December 18, 2025, 6:50pm UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/4 "2025-12-18T18:50:55Z")
Saw an update on [August 7, 2025 / ⛱️ Remote MCP Server, tons of small UI improvements](https://community.fibery.io/t/august-7-2025-remote-mcp-server-tons-of-small-ui-improvements/9371) 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](https://github.com/anthropics/claude-code/issues/12836)). 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. ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [January 18, 2026, 10:01am UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/5 "2026-01-18T10:01:47Z")
Please publish mcp full release. Currently because Fibery MCP of OpenAI requires developer mode, two issues: it cannot be used in production its fenced from memory ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/379e7af41a29a048f28c4ad8007de02b799faaf2.png) ---
**Author:** ![roBert45](https://avatars.discourse-cdn.com/v4/letter/r/c37758/32.png) [@roBert45](https://community.fibery.io/u/roBert45)\ **Post date:** [January 19, 2026, 10:55am UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/6 "2026-01-19T10:55:52Z")
Yes, it’s wise to broadcast your \*\*MCP server\*\* to the official registry right away. It guarantees that your server is trustworthy, discoverable, and prepared for the docker MCP toolkit and other tools after GA. Waiting just entails catching up. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [January 28, 2026, 1:49pm UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/7 "2026-01-28T13:49:18Z")
We submitted our MCP there ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [March 24, 2026, 9:08am UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/8 "2026-03-24T09:08:54Z")
Done > **[Official MCP Registry](https://registry.modelcontextprotocol.io/?q=fibery)** ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [March 24, 2026, 3:13pm UTC](https://community.fibery.io/t/done-publish-mcp-server-to-official-mcp-registry/9805/9 "2026-03-24T15:13:27Z")