Releases: metatool-ai/metamcp
Releases · metatool-ai/metamcp
Fix auth in nginx setup and bug fixes
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
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
OAuth & Remote Hosting
Features
- Architecture change: added remote hosting Dockerfile in https://github.com/metatool-ai/metatool-app/blob/main/remote-hosting/Dockerfile
- Supports OAuth
- In-app connection to MCP servers so you can e.g., refresh tools directly in app with default remote mode.
Tool Execution Logs
This feature is gated by TOOL_LOGS capability sent from your MetaMCP host, so no worries of leaking data.
Improve installation exp by fixing migration
Windows Compatibility and SSE transport
- After MCP official typescript SDK 1.8.0 MetaMCP is natively compatible with Windows.
- MetaMCP bumped the dependency version to make itself working with Windows natively. And also provide an option to start as standalone SSE server locally.
v0.4.0 Tool Management
- For stdio servers, rely on MetaMCP mcp server to report back listed tools
- For sse servers, allow proactive refresh of tools
- Allow enabling tool level management
- Allow toggle on/off tool level for each MCP server