docsgrep
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_workspaceB | Sets up a docsgrep base camp in the specified project directory to store temporary files, logs, and reports. Also automatically updates the .gitignore file. |
| detect_stackC | Spies on the project's technology stack by reading package manager files (e.g., package.json, composer.json, go.mod, Cargo.toml). |
| check_styleB | Sniffs out project style: conventions, linters, and infers implicit coding patterns from codebase samples. Combines convention detection and code pattern analysis. |
| find_docsB | Hunts for README files and documentation inside docs/ folders in a local directory. |
| clone_repoB | Fetches a remote git repository to a temporary directory and finds documentation. Supports authentication for private repos. |
| read_fileC | Peeks into the contents of a specific documentation or README file. |
| clear_cacheA | Purges old cached repositories from the .docsgrep workspace. Removes repos older than the specified max age (default 7 days). |
| search_docsA | Greps for a pattern within documentation files (README, docs/**/*.md) in a local directory. Returns matching lines with file path and line number. Results ranked by relevance. |
| analyze_codeC | Performs an enterprise-grade code quality audit (linting). Analyzes tech stack, conventions, and applies industry best practices. |
| lint_interactiveA | Asks what you want to lint. Generates an interactive prompt showing detected tech stack and available linting options. |
| audit_securityB | Guards your code with enterprise-grade security audit covering OWASP Top 10, ISO/IEC 27001, secrets detection, privacy (GDPR/CCPA), and dependency vulnerabilities. |
| security_interactiveB | Asks before guarding. Shows what will be scanned (OWASP Top 10, secrets, privacy, dependencies) and available options. |
| catch_bugsC | Catches bugs, errors, warnings, and potential issues in code: race conditions, memory leaks, runtime errors, dependency coupling, and performance issues. |
| semantic_searchB | Searches documentation based on meaning (semantic search), not just keyword matching. Understands natural language queries and finds relevant docs. |
| summarize_docA | Automatically summarizes specific documentation files into concise, digestible chunks. Gets the essence without the noise. |
| find_relatedC | Hunts for documentation related to a specific topic, pattern, or concept. Uses similarity matching to find docs that cover the same domain. |
| check_staleB | Sniffs out documentation that has gone stale - not updated in 30+ days or out of sync with the actual code. |
| sync_documentationA | Automatically creates or updates documentation based on code changes. Detects new methods, changed signatures, and generates doc stubs. |
| verify_docsB | Checks consistency between code and documentation. Verifies that all documented methods actually exist and that parameters match reality. |
| get_contextB | Automatically provides relevant documentation context based on what code you're currently working on. No need to ask - it just knows. |
| check_deltaA | Compares what's documented versus what's actually in the code. Shows the delta between documentation claims and implementation reality. |
| show_helpA | Provides comprehensive help for all docsgrep tools with detailed examples, common patterns, and pro tips. |
| check_artefactsA | Analyzes which documentation artifacts need updates based on recent codebase changes. Uses git diff to prioritize doc updates. |
| measure_coverageA | Measures documentation coverage (docblocks) across the codebase. Language-agnostic support for JS, TS, PHP, Python, Go, Rust, etc. |
| detect_patternsB | Maps project architectural patterns (MVC, Repository, etc.) and suggests refactoring candidates (Base Class, Trait, Interface). |
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/reasvyn/docsgrep'
If you have feedback or need assistance with the MCP directory API, please join our Discord server