2.3.5 Fix bugs and improve OpenAPI endpoints

• OpenAPI endpoints should also use middleware (to filter out inactive tools)
• OpenAPI endpoints have no concepts of session and progressive MCP server with internal states. So optimize the performance of it by having one fixed session for each OpenAPI endpoint without initiating new ones to significantly boost performance.
• Add Open WebUI docs

2.3.3 Fix inspector and namespace tools auto refresh

• Fix bugs and optimize inspector
• Let namespace save tools and auto load in first page load

docker pull ghcr.io/metatool-ai/metamcp:2.3.3

2.3.2 i18n Support zh locale

• i18n support: happy to take contributions on other languages
• Minor bug fixes

docker pull ghcr.io/metatool-ai/metamcp:2.3.2

2.2.1 User specific server, OIDC, performance and bug fixes

#82

• For better auth taking suggestions from #75
• Main feature: 1) in #70 (User specific servers, allow private and public scoping of MCP servers till endpoints, public API keys cannot access private MCPs)
• Temporarily mitigated #79
• Fixed bugs in export/import JSON
• Spawn and invalidate sessions asyncly

Following PRs will also bundled in 2.2

• #77 by @tsachis
• #80 by @divemasterza (merged by @zhjch05 )

docker pull ghcr.io/metatool-ai/metamcp:2.2.1

2.1 Live Logs, Idle Sessions, OpenAPI hosting

#74

• Live Logs which pipes stdio server's stderr and can help figure out sub MCPs logging and bugs.
• Reserve 1 idle session per MCP and MetaMCP. This will reduce cold start problem with stdio servers.
• Added support for OpenAPI hosting in addition to SSE and SHTTP, this will seamlessly work with clients like Open WebUI.

docker pull ghcr.io/metatool-ai/metamcp:2.1.1

Fix auth in nginx setup and bug fixes

#71

https://github.com/metatool-ai/metamcp/pkgs/container/metamcp/449118719?tag=2.0.6

docker pull ghcr.io/metatool-ai/metamcp:2.0.6

MetaMCP 2.0 rewritten architecture.

Overview

• Remote only and all-in-one, no local proxy needed (but you can choose to run without docker in your local machine, or use a stdio proxy with it)
• No project/workspace layer concepts, You can create MCP servers, group them together into namespaces, and assign endpoints to them.
• Complete auth.
• In house inspector to check whether MetaMCP is working or not.

Check main branch README for more details

https://github.com/metatool-ai/metamcp/pkgs/container/metamcp/447514139?tag=2.0.5

docker pull ghcr.io/metatool-ai/metamcp:2.0.5

Support Streamable HTTP MCP Servers

As title

Bug fixes & remote hosting streamable http output

Bug fixes & remote hosting streamable http output (fixed last version)
By utilizing sessionId better.

OAuth & Remote Hosting with fixed builds

v0.5.2