Add comprehensive usage guide for meta-mcp MCP server #192
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds a comprehensive guide for using the meta-mcp server with ToolHive. The meta-mcp server serves as an intelligent intermediary that provides semantic tool discovery and unified access to multiple MCP servers through a single endpoint.
Key changes:
- Complete documentation for meta-mcp setup and configuration across UI, CLI, and Kubernetes environments
- Detailed explanation of the meta-mcp workflow and its tool discovery capabilities
- Practical examples and recommended practices for optimal usage
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
ff2c7d3 to
eb703c8
Compare
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
eb703c8 to
e80a577
Compare
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
e80a577 to
13b789a
Compare
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
13b789a to
1265cfc
Compare
aponcedeleonch
left a comment
aponcedeleonch
left a comment
There was a problem hiding this comment.
Left some comments but in general it looks good to me :)
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
1265cfc to
ea337a4
Compare
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
ea337a4 to
51f6e04
Compare
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
51f6e04 to
754b72a
Compare
danbarr
left a comment
danbarr
left a comment
There was a problem hiding this comment.
A few more questions, and clarification suggestions.
Also it'll need to be run thru prettier...the repo README has the how-to. If you don't want to install npm, there's a dev container you can open in VS Code.
| thv client list-registered | ||
| ``` | ||
|
|
||
| **Step 3: Add MCP servers to the default group** |
There was a problem hiding this comment.
Question about usage: A lot of existing users will likely already have their clients registered with the default group. Will this cause an issue if both the meta-mcp and the MCPs "behind" it are available to a client?
From a workflow perspective, would reversing the usage of groups make sense? i.e., put meta-mcp into your default group (or whatever other group you use with your clients), then put the servers it's managing into the meta group and don't connect any clients to that group?
Or if that's not supported (does meta-mcp only look into the default group?), should we guide users to disconnect existing clients from the default group and use it ONLY for the MCPs that meta-mcp is managing?
There was a problem hiding this comment.
Meta-mcp server supports either of the two approaches above. Overall, the client should be configured only with the group containing the meta-mcp server.
I think our current approach (meta-mcp in meta group, other servers in default group) works well for existing users with MCP servers in default group. They need to create a new group "meta", run meta-mcp server in meta group, un-configure the clients to use the default group, and configure the clients to use the meta group.
There was a problem hiding this comment.
OK, that makes sense, but we'll need to articulate that so they know what's going on.
There was a problem hiding this comment.
With the new updates merged in, we can probably roll as-is. I think the only bit we don't explicitly say is that you shouldn't have any single client connected to BOTH the default and meta group?
There was a problem hiding this comment.
It will be good to call that out — clients should not connect to both groups. That will defeat the purpose of meta-mcp server.
This guide documents how to use the meta-mcp server with ToolHive for intelligent tool discovery and unified access to multiple MCP servers. Includes setup instructions along with practical examples and best practices. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
ptelang
force-pushed
the
add-meta-mcp-doc
branch
from
754b72a to
c589f0c
Compare
This guide documents how to use the meta-mcp server with ToolHive for intelligent tool discovery and unified access to multiple MCP servers. Includes setup instructions along with practical examples and best practices.
🤖 Generated with Claude Code
Description
Related issues/PRs
Screenshots
Merge checklist
Content
sidebars.ts) updated for added, deleted, reordered, or renamed filesvercel.jsonfor moved, renamed, or deleted pages (i.e., if the URL slug changed)Reviews