Discovery MCP server
Commit Sep 2, 2026Discovers an MCP server's tools, resources, and capabilities and outputs them as Markdown, HTML, text, JSON, or custom templates.
Also known as rust-mcp-stack/mcp-discovery
- Stars
- 88
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Sep 2, 2026
- License
- MIT
What is Discovery MCP?
Discovery discovers an MCP server's tools, resources, and capabilities and outputs them as Markdown, HTML, text, JSON, or custom templates.
Summary generated from the project's README
About Discovery MCP server
Documenting the capabilities of an MCP server is what mcp-discovery enables for developers and maintainers. This Rust-based command-line tool inspects a server to identify its tools, resources, and specific capabilities, then presents that information in various formats. It can output data directly to your terminal or generate files in Markdown, HTML, plain text, or JSON.
Users can integrate this tool into their development workflow using the GitHub Action to automate documentation updates. The utility supports remote connections via Streamable HTTP transport and handles authentication through OAuth grants, including client credentials and authorization code flows. For highly specific needs, it allows for custom Handlebars templates provided via local files, inline strings, or remote URLs.
Beyond simple creation, the update subcommand allows developers to maintain existing files by inserting fresh capability data between specific marker annotations. This ensures that README files and documentation stay synchronized with the actual server implementation without manual editing.
What you can do with it
- 1Automate documentation maintenanceUse the GitHub Action to keep your repository README files up to date with your latest server tools.
- 2Inspect remote server capabilitiesConnect to a remote MCP server over HTTP to see what tools and resources it offers.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablerust-mcp-stack/mcp-discovery is public and reachablegithub.com/rust-mcp-stack/mcp-discovery ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-02github.com/rust-mcp-stack/mcp-discovery ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCP Discovery
A command-line tool written in Rust for discovering and documenting MCP Server capabilities.
It supports outputting the results in the terminal or saving them to files in Markdown, HTML, plain text, JSON, or a custom template defined by you.
Check the project documentation for instructions and command examples.
Features 💡
- Display MCP Details: Output MCP Server information, including tools, resources, and capabilities, directly to the terminal.
- Generate Files: Create files in Markdown (
.md), HTML (.html), or plain text (.txt) formats with MCP Server details and capabilities. - Update Files: Modify existing Markdown, HTML, or text files by adding MCP Server capabilities within specified markers, enabling MCP Server developers to automatically maintain up-to-date documentation and repository README files.
- Flexible Output Customization: Choose from built-in templates (
md,md-plain,html,txt) or supply custom Handlebars templates for personalized output. - MCP Discovery GitHub Action: Integrate the mcp-discovery CLI as a GitHub Action to automate and maintain up-to-date MCP Server documentation in your development workflow.
This open-source project leverages the rust-mcp-sdk for seamless interaction with MCP Servers.
🌐 Check out the rust-mcp-filesystem capabilities page for a sample output.
Installation ⬇️
Running as CLI
Check the project documentation for instructions on installing the tool on different platforms.
GitHub Action
The easiest way to automate and maintain up-to-date MCP Server documentation , is to use mcp-discovery as a GitHub action. Please see rust-mcp-stack/mcp-discovery-action for installation and configuration instructions.
Subcommands
print: Displays MCP Server capabilities in the terminal.create: Creates a new file with MCP Server capability details.update: Updates an existing file by inserting MCP Server capabilities between specified markers.
👉 Note: If no subcommand is provided, the print subcommand will be used by default.
Options ⚙️
-f, --filename <FILENAME>: Used withcreateandupdatecommands to specify the output file to generate or modify.-t, --template <TEMPLATE>: Choose a built-in output template. Options:md,md-plain,html,txt.-p, --template-file <TEMPLATE_FILE>: Path to a custom Handlebars template file, or a folder containingtemplate.hbswith an optional siblingpartials/directory.-s, --template-string <TEMPLATE_STRING>: Inline Handlebars template provided as a string.--template-url <URL>: Fetch and render a Handlebars template from anhttps://URL (.hbs,.zip, or.tar.gz). Supports fragment directives:#sha256=<hex>(integrity pin) and#entry=<subpath>(select a file inside an archive).--cache-dir <PATH>: Cache directory for templates fetched with--template-url(created if missing; defaults to the OS cache dir).-l, --log-level <LOG_LEVEL>: Specifies the logging level (default:info). Options:error,warn,info,debug,trace.--template-file/archive templates can use their own partials from apartials/folder — see the Custom Templates guide.--url <URL>: Connect to a remote MCP server over the Streamable HTTP transport.--header "Name: Value": Static HTTP header for the Streamable HTTP transport (repeatable).--grant <GRANT>: OAuth grant for protected servers:client-credentials(default) orauthorization-code.--client-id <ID>: Pre-registered OAuth client id (omit to use Dynamic Client Registration).--client-secret <SECRET>: Pre-registered OAuth client secret.--scope <SCOPE>: OAuth scope(s) to request.--redirect-uri <URI>: Redirect URI for theauthorization-codegrant.-h, --help: Display help information.-V, --version: Display the version ofmcp-discovery.
👉 Note: If no template is provided, mcp-discovery will automatically select the most suitable built-in template based on the file extension.
👉 Note: Authentication flags require --url. See the Authentication guide for examples of connecting to open, token-protected, and OAuth-protected MCP servers.
Built-in Templates 🧬
The CLI supports the following built-in output templates:
md: Formatted Markdown that presents MCP Server capabilities in a table format.md-plain: Minimalist Markdown for straightforward output, using plain text instead of tables.html: Structured HTML with basic styling.txt: Plain text for raw, unformatted output.
Custom Templates 🧩
You can provide custom Handlebars templates in different ways:
- Use the
--template-fileflag to provide a custom template file, or a folder containingtemplate.hbswith an optional siblingpartials/directory. - Use the
--template-stringflag to provide a raw Handlebars template directly as a string. - Use the
--template-urlflag to fetch a Handlebars template (.hbs,.zip, or.tar.gz) from anhttps://URL. Supports fragment directives:#sha256=<hex>(integrity pin) and#entry=<subpath>(select a file inside an archive). See the Remote templates guide for details. - To use an inline template, define it in a file for the
updatecommand only — this will not function with print or create.
Inline templates must be enclosed within designated marker annotations.
Examples
Print MCP Server capabilities to the terminal:
mcp-discovery -- npx -y @modelcontextprotocol/server-everything
Create a HTML file with MCP Server capabilities:
mcp-discovery create -f capabilities.html -- npx -y @modelcontextprotocol/server-everything
📄 Click here to view generated html file
Create a MD file with MCP Server capabilities:
mcp-discovery create -f capabilities.md -- npx -y @modelcontextprotocol/server-everything
Use a custom Handlebars template:
mcp-discovery create -f capabilities.md --template-file=custom_template.hbs -- npx -y @modelcontextprotocol/server-everything
💡 See the Command Examples section in the project documentation for additional CLI usage examples.
Defining Update Regions with Markers
When using the update subcommand, mcp-discovery places capabilities between designated markers in the target file, which vary by file format and are typically comment lines.
The update command simplifies the process for developers and maintainers to keep documentation current effortlessly.
Run the mcp-discovery update command anytime to refresh the file with the latest MCP Server capabilities.
Marker Annotations
- Render Block Start :
mcp-discovery-render - Render Block End :
mcp-discovery-render-end
👉 The mcp-discovery-render marker supports template and template-file properties as well. Check the examples below for details.
You can optionally include an inline template identifier within the render block, enclosed by:
- Template Block Start:
mcp-discovery-template - Template Block End:
mcp-discovery-template-end
If a template annotation is detected within a render block, mcp-discovery will use it to render the output. This allows for customized templates without depending on built-in or external template files. Check the examples below for details:
Sample Markdown file annotated with render block:
# Server Info and Capabilities
<!-- mcp-discovery-render -->
Server Capabilities will be placed here...
<!-- mcp-discovery-render-end -->
Sample Markdown file, annotated with render block and template name:
# Server Info and Capabilities
<!-- mcp-discovery-render template=md-plain -->
Server Capabilities will be placed here...
<!-- mcp-discovery-render-end -->
Sample Markdown file, annotated with render block and custom template file:
# Server Info and Capabilities
<!-- mcp-discovery-render template=my-custom-template.hbs -->
Server Capabilities will be placed here...
<!-- mcp-discovery-render-end -->
Sample HTML file with annotations :
<!DOCTYPE html>
<html lang="en">
<head>
<title>My MCP Server</title>
</head>
<body>
<h1>MCP Server Details</h1>
<div>
<!-- mcp-discovery-render -->
<!-- mcp-discovery-render-end -->
</div>
</body>
</html>
Sample HTML file with inline template :
<h1>MCP Server Details</h1>
<div>
<!-- mcp-discovery-render -->
<!-- mcp-discovery-template
<b>Name: </b>{{name}}
<br/>
<b>Version: </b>{{version}}
<br/>
<b>Number of tools:</b> {{len tools}}
<h2>Summary:</h2>
{{> html-summary }}
mcp-discovery-template-end -->
<!-- mcp-discovery-render-end -->
</div>
Below is a screenshot showing the resulting HTML after the mcp-discovery update command is executed:
You can execute the mcp-discovery update command whenever you need to refresh the file with the latest MCP Server capabilities.
Contributing
We welcome everyone who wishes to contribute! Please refer to the contributing guidelines for more details.
All contributions, including issues and pull requests, must follow Rust's Code of Conduct.
Unless explicitly stated otherwise, any contribution you submit for inclusion in mcp-discovery is provided under the terms of the MIT License, without any additional conditions or restrictions.
License
This project is licensed under the MIT License. see the LICENSE file for details.
Discovery MCP questions
What does mcp-discovery do?
It connects to an MCP server and documents its capabilities, listing server information, tools, and resources. Results can be printed to the terminal or written to files.
Does mcp-discovery support OAuth-protected MCP servers?
Yes. It offers OAuth grant options such as client-credentials or authorization-code, plus client id, secret, scope, and redirect URI flags when connecting with --url.
Can I run mcp-discovery in CI?
Yes, it is available as a GitHub Action so documentation can be regenerated automatically in your workflow.