docs-assistant-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Your Anthropic API key. Required for analyze_project and generate_readme's narrated sections; validated against Anthropic key shape (sk-ant-...) at startup. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_projectA | Scan a project (source tree, git history, package manifests, env files, existing docs) and return a grounded architect-level analysis: summary, architecture, technologies, complexity, documentation coverage, risk findings, and recommendations. Every claim traces back to a fact the scan actually computed — never fabricated. |
| generate_env_docsA | Document every environment variable a project declares (.env.example/.env.sample/.env.template) or reads in source (process.env/os.environ/os.Getenv), each with its required/default/example — secret-shaped values are never echoed, only redacted placeholders. |
| generate_changelogA | Generate a Markdown changelog from real git history, grouped into Breaking Changes/Features/Fixes/Other via conventional-commit types — a reformatting of commit messages that already exist, never invented entries. Optionally scoped between fromRef/toRef (e.g. two tags). |
| generate_readmeA | Generate a professional README.md grounded in the real project (source, dependencies, git history, env vars, existing docs). Overview/Features/Usage/Troubleshooting are narrated but every claim traces to a fact; Installation/Configuration/Contributing/License are generated deterministically from facts alone. |
| review_documentationA | Score a project's existing documentation on coverage/quality/consistency (0-100 each, computed deterministically from headings/word counts/topic coverage) and list missing sections and recommendations. Works against hand-written docs alone — no other generator tool needs to have run first. |
| generate_architectureB | Generate Architecture.md grounded in the real project: layers/modules from actual directory structure, a dependency graph from real relative-import statements, design-pattern evidence from real class names, tech stack, and recorded ADRs. The overview paragraph is narrated but every claim traces to a fact; the graphs/lists are rendered deterministically. |
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/HARDIK-31/docs-assistant-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server