update-mcp-docs

To automatically update MCP server tool documentation, you can use a script that fetches the current list of tools, descriptions, and input schemas directly from the running server and regenerates the relevant section in docs/mcp.md.

Syncing Model Context Protocol tool descriptions involves introspecting the running MCP server to fetch available tools and formatting their names, descriptions, and arguments into a readable markdown table within your documentation.

Yes, the MCP documentation sync process requires a running MCP server because the script needs to fetch the actual list of available tools, their descriptions, and input schemas directly from the live server instance.

To generate markdown tables for MCP API tools, the automation script extracts the tool name, description, and arguments from the server and formats them into a readable markdown table to update your documentation file.

MCP documentation becomes outdated after adding new tools because the docs/mcp.md file is static and requires a synchronization process to fetch the newly exposed tools and regenerate the markdown table for accuracy.