code-auditor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODE_AUDITOR_DATA_DIR | No | Directory to use as the storage root for the code index database. |
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 |
|---|---|
| auditA | Fetch paginated results for a completed audit by resultId (or auditId alias). This tool never starts a new audit. |
| start_auditA | Start a background audit job. Returns immediately with a jobId. Poll audit_status until completed, then fetch pages with audit or audit_results. |
| audit_statusA | Get current status for a previously started background audit job. Returns resultId when completed. |
| audit_resultsA | Fetch paginated violations for a completed audit result by resultId. |
| audit_healthC | Quick health check of a codebase with key metrics |
| search_codeA | Search indexed functions and React components with natural language queries. Supports operators: entity:component, component:functional|class|memo|forwardRef, hook:useState|useEffect|etc, prop:propName, dep:packageName, dependency:lodash, uses:express, calls:functionName, calledby:functionName, dependents-of:functionName, used-by:functionName, depends-on:module, imports-from:file, unused-imports, dead-imports, type:fileType, file:path, lang:language, complexity:1-10, jsdoc:true|false |
| find_definitionA | Find the exact definition of a specific function or React component |
| sync_indexA | Synchronize, cleanup, or reset analysis-derived data (indexed functions, FlexSearch, cached audits, code maps, schema overlays). Project tasks, analyzer configs, and whitelist entries are preserved on reset. |
| generate_ai_configA | Generate configuration files for AI coding assistants |
| get_workflow_guideA | Get recommended workflows and best practices for using code auditor tools effectively |
| set_analyzer_configA | Set or update analyzer configuration that persists across audit runs |
| get_analyzer_configB | Get current configuration for an analyzer |
| reset_analyzer_configC | Reset analyzer configuration to defaults |
| get_code_map_sectionB | Retrieve a specific section of a previously generated code map |
| list_code_map_sectionsB | List all available sections for a code map |
| project_tasksA | Manage a persistent per-project task queue. Tasks and analyzer configs survive sync_index reset; reset clears function index, cached audits, code maps, and schema overlays (no ghost code references). Use delete to remove a task. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose; even closely related tools like audit and audit_results are separated by 'results' vs 'violations', and descriptions clarify usage without ambiguity.
All tool names use consistent snake_case and mostly follow a verb_noun pattern (e.g., search_code, start_audit), with no mixing of naming conventions.
With 16 tools, it slightly exceeds the typical 3-15 range, but the comprehensive code auditing domain justifies the count, covering audit lifecycle, config, search, code maps, tasks, and maintenance.
Core workflows are well-covered (audit start/status/results, config CRUD, search, code maps), though missing a stop audit or list all audits option, which are minor gaps.