MCP Discovery MCP Server
Automate the discovery and documentation of your MCP Servers for reliable, always-up-to-date technical references using MCP Discovery.

What does “MCP Discovery” MCP Server do?
MCP Discovery is a command-line tool written in Rust designed to discover and document the capabilities of MCP (Model Context Protocol) Servers. It serves as an interface for launching MCP Servers using specified commands and then querying them for their available tools, resources, and other capabilities. The tool outputs the gathered information either directly to the terminal or saves it into Markdown, HTML, or plain text files, making it easier for developers to generate, update, and maintain comprehensive documentation for their MCP Servers. MCP Discovery enhances AI development workflows by automating the exploration and documentation of server features, ensuring consistent and up-to-date information is available for integration with external data sources, APIs, and services.
List of Prompts
No information about prompt templates is available in the provided repository or documentation.
List of Resources
No information about specific resources exposed by MCP Discovery is available in the provided repository or documentation.
List of Tools
No explicit server tools are described in the repository or documentation.
Use Cases of this MCP Server
MCP Server Capability Documentation
Automate the discovery and documentation of MCP Server capabilities, tools, and resources, ensuring that documentation is always current and accurate.Repository README Maintenance
Update existing Markdown, HTML, or text files (such as README files) with up-to-date MCP Server capabilities, reducing manual editing and human error.Custom Output Generation
Generate documentation files in various formats (Markdown, HTML, plain text) using built-in or custom templates, enabling seamless integration into different documentation workflows.Continuous Documentation Integration
Use as a GitHub Action to automatically maintain and update MCP Server documentation as part of continuous integration (CI) pipelines.
How to set it up
Windsurf
- Ensure you have Rust and Cargo installed on your system.
- Follow the installation instructions for your platform.
- Configure Windsurf to run the
mcp-discovery
executable as part of its workflow. - Add the MCP Discovery server to your configuration (example below).
- Save and restart Windsurf as needed.
Example JSON configuration:
{
"mcpServers": {
"mcp-discovery": {
"command": "mcp-discovery",
"args": ["--output", "md"]
}
}
}
Claude
- Install Rust and Cargo on your system.
- Install MCP Discovery by following the documentation.
- Add MCP Discovery as a server in Claude’s configuration.
- Save your configuration and restart Claude.
Example JSON configuration:
{
"mcpServers": {
"mcp-discovery": {
"command": "mcp-discovery",
"args": ["--output", "md"]
}
}
}
Cursor
- Install Rust and Cargo as prerequisites.
- Download and install MCP Discovery per the official guide.
- Edit Cursor’s configuration to add MCP Discovery.
- Save the configuration and restart Cursor.
Example JSON configuration:
{
"mcpServers": {
"mcp-discovery": {
"command": "mcp-discovery",
"args": ["--output", "md"]
}
}
}
Cline
- Make sure Rust and Cargo are installed.
- Install MCP Discovery by following the project documentation.
- Configure Cline to include MCP Discovery as a server.
- Save configuration and restart as required.
Example JSON configuration:
{
"mcpServers": {
"mcp-discovery": {
"command": "mcp-discovery",
"args": ["--output", "md"]
}
}
}
Note:
To secure API keys or sensitive information, use environment variables in your configuration. Example:
{
"mcpServers": {
"mcp-discovery": {
"command": "mcp-discovery",
"args": ["--output", "md"],
"env": {
"API_KEY": "${API_KEY}"
},
"inputs": {
"apiKey": "${API_KEY}"
}
}
}
}
How to use this MCP inside flows
Using MCP in FlowHunt
To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:
{
"mcp-discovery": {
"transport": "streamable_http",
"url": "https://yourmcpserver.example/pathtothemcp/url"
}
}
Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “mcp-discovery” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.
Overview
Section | Availability | Details/Notes |
---|---|---|
Overview | ✅ | |
List of Prompts | ⛔ | No prompt templates found |
List of Resources | ⛔ | No resources listed |
List of Tools | ⛔ | No explicit tools described |
Securing API Keys | ✅ | Example provided in setup instructions |
Sampling Support (less important in evaluation) | ⛔ | Not mentioned |
Our opinion
MCP Discovery is a robust documentation utility, but as an MCP “Server” it does not expose typical resources, prompts, or tools. Its strength lies in documentation automation and integration, but its utility as an LLM-facing MCP server is limited. For its intended purpose, it is well-built, but as a model context protocol server, it is less relevant.
Rating: 4/10
MCP Score
Has a LICENSE | ✅ (MIT) |
---|---|
Has at least one tool | ⛔ |
Number of Forks | 0 |
Number of Stars | 14 |
Frequently asked questions
- What is the main function of MCP Discovery?
MCP Discovery automates the process of discovering and documenting the capabilities, tools, and resources of MCP Servers. It outputs this information in Markdown, HTML, or text formats for easy integration into documentation workflows.
- Can MCP Discovery be used as a standard MCP Server for LLMs?
While MCP Discovery acts as a server interface, it is primarily a documentation utility and does not expose traditional tools, prompts, or resources for LLMs. Its main strength is in documentation automation.
- How do I secure API keys in my MCP configuration?
Store sensitive keys using environment variables in your server configuration. For example, use 'env' and 'inputs' sections to reference variables like ${API_KEY} instead of hardcoding secrets.
- Does MCP Discovery support continuous documentation integration workflows?
Yes, MCP Discovery can be used as part of CI pipelines (e.g., as a GitHub Action) to automatically generate and update server documentation, ensuring information is always current.
- What formats can MCP Discovery output documentation in?
MCP Discovery supports outputting documentation in Markdown, HTML, and plain text, using built-in or custom templates for seamless integration into your documentation system.
Start Automating Your MCP Server Documentation
Effortlessly generate, update, and maintain comprehensive documentation for your MCP Servers with MCP Discovery. Integrate into your CI workflow for continuous, reliable updates.