| name | mcp-tools-catalog |
| description | Build docs/mcp-tools.md from the active MCP servers and available tool functions. |
| metadata | [object Object] |
MCP Tools Catalog
Create a project-local catalog of MCP tools at docs/mcp-tools.md.
Core rules
- Use the runtime MCP tool list and enabled server list to generate the catalog.
- Draft in chat first; ask for one confirmation before writing any files.
- Do not edit other files.
- Exception: if
AGENTS.mdlacks a reference todocs/mcp-tools.md, include that update under the same confirmation.
Steps
- Run:
codex mcp list --jsonto get enabled server names. - Use prompt-engineering to list the tool functions currently available right now using this exact prompt:
list the functions that is CURRENTLY avalible to you **RIGHT NOW**, starting with the prefix `functions.mcp__`
after each function, provide a clear, concise, and informative overview of what each function is intended for
- Map tool functions to
server:toolnames (e.g.,playwright:browser_click). - Filter out any tools whose server is not enabled.
- Build
docs/mcp-tools.mdusingassets/mcp-tools-template.md. - If
AGENTS.mdlacks a reference todocs/mcp-tools.md, include that change in the draft summary. - Ask: "Reply CONFIRM to write docs/mcp-tools.md and update AGENTS.md (if needed)."
- On confirmation, write the file and update
AGENTS.mdif missing the reference.
Output requirements
- Use
server:toolnaming per line. - Include a short description for each tool.
- Include a list of enabled servers at the top.