Generate-documentation-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_documentationA | Generate a Markdown documentation skeleton from Git changes. Args: project_path: Path to the Git repository. Defaults to the server's current working directory (the project Claude Code is running in). include: Glob patterns; only matching changed files are documented (e.g. [".py", "src/**"]). If omitted, all changed files match. exclude: Glob patterns to drop from the result (e.g. [".css"]), applied after include. output_file: Path (relative to project_path, unless absolute) for the generated Markdown file. language: Skeleton language, "en" or "pt". title: Document title. Defaults to a language-appropriate title. template: Template name to render (see templates/ directory). mode: Diff source — "working_tree" (uncommitted changes, default), "commit" (a single commit), or "branch" (current branch vs base_branch). commit_hash: Commit to document when mode="commit". Defaults to HEAD. base_branch: Base branch to diff against when mode="branch" (uses base_branch...HEAD). Defaults to "origin/main". Returns: {"success": bool, "output_file": str | None, "files_processed": int, "files_ignored": int, "error": str (only on failure)} |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Paulosouzx/mcp-gen-documentation'
If you have feedback or need assistance with the MCP directory API, please join our Discord server