project-graph-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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_skeletonA | Get compact minified project overview (10-50x smaller than source). Returns legend, stats, node summaries, file imports, and W web component summaries when present. |
| get_focus_zoneB | Get enriched context for recently modified files. Auto-detects from git or accepts explicit file list. |
| get_ai_contextA | Boot AI agent context. Two modes:
|
| invalidate_cacheA | Invalidate the cached graph. Use after making code changes. |
| get_usage_guideA | Get the comprehensive usage guide for project-graph with examples and best practices. Call this FIRST when planning how to analyze, navigate, or audit a codebase. Returns practical examples and recommended workflow for each feature area. Available topics: navigation, analysis, testing, documentation, rules, workflow. Omit topic to get the full guide. |
| get_agent_instructionsA | Get coding guidelines, architectural standards, and JSDoc rules for this project. |
| get_custom_rulesA | List all custom code analysis rules. Rules are stored in JSON files in rules/ directory. |
| set_custom_ruleA | Add or update a custom code analysis rule. Creates ruleset if it does not exist. |
| check_custom_rulesB | Run custom rules analysis on a directory. Returns violations found. |
| get_framework_referenceA | Get framework-specific AI reference documentation. Auto-detects framework from project or accepts explicit name. Returns full API reference, patterns, and common mistakes as agent context. |
| graph_metadataC | Read and validate project-local graph metadata sidecar. Actions: get|validate |
| navigateB | Navigate the project graph. Actions: expand|deps|usages|call_chain|sub_projects. deps returns code calls plus web template/style/component links when present. |
| analyzeC | Code quality analysis. Actions: dead_code|similar_functions|complexity|large_files|outdated_patterns|full_analysis|analysis_summary|undocumented |
| testingC | Test checklist management. Actions: pending|pass|fail|summary|reset |
| filtersC | Filter configuration. Actions: get|set|add_excludes|remove_excludes|reset |
| jsdocC | JSDoc operations. Actions: check_consistency|check_types|generate |
| docsC | Documentation (.ctx) management. Actions: get|generate|check_stale|validate_contracts |
| compactD | Compact code operations. Actions: compact_file|edit|compact_all|beautify|expand_file|expand_project|validate_pipeline|get_mode|set_mode |
| dbC | Database analysis. Actions: schema|table_usage|dead_tables |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Project Graph Usage Guide | Comprehensive guide with workflows and examples |
TDQS
Scored across 19 tools
Each tool targets a distinct functional area: context provision, navigation, analysis, documentation, custom rules, testing, and caching. Even similar tools like get_skeleton and get_ai_context have clearly differentiated purposes (skeleton-only vs. full context), eliminating ambiguity.
Tool names mix single-word domain identifiers (docs, compact, db, jsdoc, navigate, analyze, testing, filters) with snake_case verb phrases (get_focus_zone, invalidate_cache, set_custom_rule). While descriptive, the lack of a uniform verb_noun or noun_verb pattern across all tools makes naming slightly inconsistent.
The 19 tools are slightly above the ideal 3-15 range, but the server's broad scope (code graph navigation, analysis, documentation, testing, custom rules, AI context) justifies the count. Each tool serves a clear purpose, and no tool feels redundant.
The tool set provides comprehensive coverage of codebase analysis and AI assistance: navigation, quality analysis, test tracking, documentation management, custom rules, and context generation. Minor gaps like a missing delete_custom_rule are workable and do not create dead ends.