Updated meta-mcp doc with the latest features #244
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull Request Overview
This update enhances the meta-mcp documentation to reflect new features that improve the server's capability to dynamically manage MCP servers. The key change is documenting meta-mcp's ability to automatically discover and install missing MCP servers from the ToolHive registry when needed.
Key changes:
- Enhanced description of dynamic server installation capabilities
- Updated workflow documentation to include scenarios for both installed and missing MCP servers
- Clarified routing behavior and tool discovery processes
ptelang
force-pushed
the
update-meta-mcp-doc
branch
from
b4fbe6b to
6db2473
Compare
ptelang
force-pushed
the
update-meta-mcp-doc
branch
from
6db2473 to
b2f13ae
Compare
ptelang
force-pushed
the
update-meta-mcp-doc
branch
from
b2f13ae to
4a375a2
Compare
ptelang
force-pushed
the
update-meta-mcp-doc
branch
from
4a375a2 to
6953ea5
Compare
ptelang
force-pushed
the
update-meta-mcp-doc
branch
from
6953ea5 to
31d6e2a
Compare
ptelang
force-pushed
the
update-meta-mcp-doc
branch
from
31d6e2a to
ab417d7
Compare
ptelang
force-pushed
the
update-meta-mcp-doc
branch
from
ab417d7 to
bdba60d
Compare
|
|
||
| ## Deployment in Kubernetes | ||
|
|
||
| Meta-mcp is supported in Kubernetes enviornment. Follow |
There was a problem hiding this comment.
Corrected spelling of 'enviornment' to 'environment'.
| Meta-mcp is supported in Kubernetes enviornment. Follow | |
| Meta-mcp is supported in Kubernetes environment. Follow |
Copilot uses AI. Check for mistakes.
|
|
||
| ## Advanced configuration using environment variables | ||
|
|
||
| Meta-mcp server can be configured using following enviornment variables. |
There was a problem hiding this comment.
Corrected spelling of 'enviornment' to 'environment'.
| Meta-mcp server can be configured using following enviornment variables. | |
| Meta-mcp server can be configured using following environment variables. |
Copilot uses AI. Check for mistakes.
| thv group create meta | ||
|
|
||
| # Run meta-mcp in the dedicated group | ||
| # Run meta-mcp in the dedicated group with access to server from all groups |
There was a problem hiding this comment.
| # Run meta-mcp in the dedicated group with access to server from all groups | |
| # Run meta-mcp in the dedicated group with access to servers in all other groups |
| </TabItem> | ||
| </Tabs> | ||
|
|
||
| ## Deployment in Kubernetes |
There was a problem hiding this comment.
Can this be moved into a "Kubernetes" tab like in the template?
Also this section needs to be run thru prettier to fix the formatting issues blocking the CI.
|
|
||
| :::tip[Other versions] | ||
|
|
||
| Version 0.0.8 is shown above, but other versions are available. You can browse all available versions on the [meta-mcp releases page](https://github.com/StacklokLabs/meta-mcp/releases) or list them using: |
There was a problem hiding this comment.
Suggestion: could default to leaving the --version flag off the helm command in the initial example so users get the latest version if they just copy-paste, then note that it can be used to install a specific version? As a comparison/reference, that's the pattern used in the main Operator installation guide.
| ```bash | ||
| # macOS | ||
| brew install crane | ||
|
|
||
| # Then list tags | ||
| crane ls ghcr.io/stackloklabs/meta-mcp/meta-mcp | ||
| ``` |
There was a problem hiding this comment.
We support Windows and Linux too; instead of making this longer to accommodate those, IMO just directing users to the releases page is sufficient.
| - **Intelligent routing**: Automatically routes requests to the appropriate MCP | ||
| server based on tool requirements | ||
| - **Intelligent routing**: Routes requests to the requested MCP server and tool | ||
| - **Dynamic Server Installation**: Automatically discovers and installs missing |
There was a problem hiding this comment.
| - **Dynamic Server Installation**: Automatically discovers and installs missing | |
| - **Dynamic server installation**: Automatically discovers and installs missing |
| multiple MCP servers. | ||
|
|
||
| The meta-mcp workflow: | ||
| The meta-mcp workflow when relevant MCP server is installed: |
There was a problem hiding this comment.
| The meta-mcp workflow when relevant MCP server is installed: | |
| The meta-mcp workflow when a relevant MCP server is already installed: |
| tool | ||
| 5. Results are returned from meta-mcp to the client | ||
|
|
||
| The meta-mcp workflow when relevant MCP server is not installed: |
There was a problem hiding this comment.
| The meta-mcp workflow when relevant MCP server is not installed: | |
| The meta-mcp workflow when no relevant MCP server is found: |
| 8. AI client requests installation of a MCP server | ||
| 9. Meta-mcp server installs the MCP server automatically if no security | ||
| credentials are needed. If security credentials are needed, meta-mcp server | ||
| guides the user to ToolHive for entering the credentials |
There was a problem hiding this comment.
| guides the user to ToolHive for entering the credentials | |
| guides the user to ToolHive to enter the credentials |
Though, from what I understand, this deep-linking will not be part of the initial launch?
| - MAX_TOOLS_TO_RETURN: Number of tools to return from find_tool (default: 8) | ||
| - TOOL_DISTANCE_THRESHOLD: Distance threshold for tool similarity (default: 1.0) | ||
| - MAX_TOOL_RESPONSE_TOKENS: Maximum number of tokens to return from call_tool | ||
| (default: None) | ||
| - WORKLOAD_POLLING_INTERVAL: Polling interval for running MCP servers (default: | ||
| 60 seconds) | ||
| - REGISTRY_POLLING_INTERVAL: Polling interval for ToolHive registry (default: 24 | ||
| hours) | ||
| - RUNTIME_MODE: Runtime mode for MCP servers: docker or k8s (default: docker) |
There was a problem hiding this comment.
| - MAX_TOOLS_TO_RETURN: Number of tools to return from find_tool (default: 8) | |
| - TOOL_DISTANCE_THRESHOLD: Distance threshold for tool similarity (default: 1.0) | |
| - MAX_TOOL_RESPONSE_TOKENS: Maximum number of tokens to return from call_tool | |
| (default: None) | |
| - WORKLOAD_POLLING_INTERVAL: Polling interval for running MCP servers (default: | |
| 60 seconds) | |
| - REGISTRY_POLLING_INTERVAL: Polling interval for ToolHive registry (default: 24 | |
| hours) | |
| - RUNTIME_MODE: Runtime mode for MCP servers: docker or k8s (default: docker) | |
| - `MAX_TOOLS_TO_RETURN`: Number of tools to return from find_tool (default: `8`) | |
| - `TOOL_DISTANCE_THRESHOLD`: Distance threshold for tool similarity (default: | |
| `1.0`) | |
| - `MAX_TOOL_RESPONSE_TOKENS`: Maximum number of tokens to return from call_tool | |
| (default: `None`) | |
| - `WORKLOAD_POLLING_INTERVAL`: Polling interval for running MCP servers, in | |
| seconds (default: `60`) | |
| - `REGISTRY_POLLING_INTERVAL`: Polling interval for ToolHive registry, in | |
| seconds (default: `86400`, 24 hours) | |
| - `RUNTIME_MODE`: Runtime mode for MCP servers: `docker` or `k8s` (default: | |
| `docker`) |
3 participants
Description
New features implemented in meta-mcp server.
Related issues/PRs
https://github.com/StacklokLabs/meta-mcp/pull/92
https://github.com/StacklokLabs/meta-mcp/pull/82
https://github.com/StacklokLabs/research/issues/79
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