MCP Discovery Action

What is MCP Discovery Action?

MCP Discovery Action is a GitHub Action that runs the MCP Discovery CLI to create, update, or print MCP server capability details in a Markdown or other formatted file. It is built for developers using MCP servers who want to automatically generate documentation of their server’s capabilities.

How to use MCP Discovery Action?

Add the action to a GitHub Actions workflow with the rust-mcp-stack/mcp-discovery-action@v1 step. Required inputs are command (e.g., create, update, or print) and mcp-launch-command (the command to start your MCP server). Optional inputs include filename, template, template-file, template-string, log-level, token, and version. See the README examples for typical workflows.

Key features of MCP Discovery Action

• Runs the MCP Discovery CLI to extract server capabilities
• Supports create, update, and print commands
• Built-in output templates: md, md-plain, html, txt
• Accepts custom Handlebars template files or template strings
• Configurable CLI version (defaults to latest)
• Optional GitHub token for committing changes

Use cases of MCP Discovery Action

• Automatically generate a mcp-discovery.md file with MCP server capabilities
• Update a designated section of an existing README.md with server details
• Customize output formatting with built-in templates or Handlebars

FAQ from MCP Discovery Action

Which inputs are required?

command and mcp-launch-command are required. All other inputs are optional.

What output templates are available?

Built-in templates: md, md-plain, html, txt. You can also provide a custom Handlebars template file or a template string.

Can I use a specific version of the MCP Discovery CLI?

Yes, set the version input to a tag like v0.1.2. Default is latest.

Does the action need write permissions to commit output?

Yes, the default token (${{ github.token }}) requires contents: write permission if you want the action to commit file changes.

How do I update a specific section of a file?

Use the update command together with MCP Discovery template markers in your target file. See the MCP Discovery documentation for details.