io.github.tosin2013/mcp-adr-analysis-server
NPM · MCP-ADR-ANALYSIS-SERVER
ADR drift detection, content safety, and decision memory for architectural decisions
Available components
Last scanned (1 hour ago)
Scores higher than 99% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 42 of 133 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to tosin2013/mcp-adr-analysis-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 9397 tokens (~105/item across 89 items; 63 tools + 26 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 63 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 64 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 +57
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Dependency health: unverified → 0.88 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 2.14.13 → 2.14.19 functional
- 28 Oct 26 −57
- Known CVEs: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Dependency health: 0.88 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 2.14.13 → 2.14.19 functional
- Package version: 2.14.13 → 2.14.16 functional
- 24 Oct 26 0
- CVE-2026-93687 no longer affects this package ▲ security
- Known CVEs: partial → pass ▲ security
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/mcp-adr-analysis-server@2.14.19
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | tosin2013/mcp-adr-analysis-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/tosin2013/mcp-adr-analysis-server/.github/workflows/publish.yml@refs/tags/v2.14.19 |
| Rekor log index | 3546934480 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1f22341ec5816c65d1c7c3d48b1ff23c12e4ed8d3de50debbec6fec3e47f472f1ca1ab5cad093f29141ec307215b1a6f947d25bf47398e9000d450330 |
Background: How many MCP packages publish verified provenance →
Dependencies 133 packages
| Packages resolved | 133 |
|---|---|
| Stale | 42 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_adr_timeline ~170
Analyze ADR timeline with smart time tracking, adaptive thresholds, and actionable recommendations. Auto-detects project context (startup/growth/mature) and generates prioritized work queue based on staleness, implementation lag, and technical debt.
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| autoDetectContext | boolean | – | Auto-detect project phase from git activity and ADR patterns |
| forceExtract | boolean | – | Force timeline extraction even if ADRs have dates |
| generateActions | boolean | – | Generate actionable work items with priority and effort estimates |
| includeContent | boolean | – | Include ADR content for better analysis |
| projectPath | string | – | Path to the project directory |
| thresholdProfile | string | – | Threshold profile for action generation (auto-detected if not specified) |
No output schema declared.
No examples provided.
analyze_content_security ~120
Analyze content for sensitive information using AI-powered detection with optional memory integration for security pattern learning
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content to analyze for sensitive information |
| contentType | string | – | Type of content being analyzed |
| enableMemoryIntegration | boolean | – | Enable memory entity storage for security pattern learning and institutional knowledge building |
| enhancedMode | boolean | – | Enable advanced prompting features |
| knowledgeEnhancement | boolean | – | Enable Generated Knowledge Prompting for security and privacy expertise |
| userDefinedPatterns | array | – | User-defined sensitive patterns to detect |
No output schema declared.
No examples provided.
analyze_deployment_progress ~152
Analyze deployment progress and verify completion with outcome rules
| Name | Type | Req | Description |
|---|---|---|---|
| actualOutcomes | array | – | Actual deployment outcomes |
| adrDirectory | string | – | Directory containing ADR files |
| analysisType | string | – | Type of deployment analysis to perform |
| cicdLogs | string | – | CI/CD pipeline logs for analysis |
| cicdStatus | object | – | CI/CD pipeline status data |
| deploymentTasks | array | – | Deployment tasks for progress calculation |
| environmentStatus | object | – | Environment status data |
| outcomeRules | array | – | Outcome rules for completion verification |
| pipelineConfig | string | – | CI/CD pipeline configuration |
| todoPath | string | – | Path to TODO.md file for task identification |
No output schema declared.
No examples provided.
analyze_environment ~144
Analyze environment context and provide optimization recommendations with optional memory integration for environment snapshot tracking
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| analysisType | string | – | Type of environment analysis to perform |
| currentEnvironment | object | – | Current environment specifications (for compliance analysis) |
| enableMemoryIntegration | boolean | – | Enable memory entity storage for environment snapshot tracking and historical analysis |
| enableTrendAnalysis | boolean | – | Enable analysis of environment changes over time using stored snapshots |
| industryStandards | array | – | Industry standards to assess compliance against |
| projectPath | string | – | Path to project directory |
| requirements | object | – | Environment requirements (for compliance analysis) |
No output schema declared.
No examples provided.
analyze_gaps ~175
Scan local codebase and compare with ADRs to detect bi-directional gaps. Finds: (1) ADR-to-code gaps: file references in ADRs that do not exist, (2) Code-to-ADR gaps: technologies in package.json and architectural patterns without ADR coverage. Reports gaps to ADR Aggregator for tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| excludePatterns | array | – | File patterns to exclude from scan (regex) |
| includeDismissed | boolean | – | Include previously dismissed gaps in analysis |
| includePatterns | array | – | File patterns to include in scan (regex) |
| projectPath | string | – | Project path (defaults to PROJECT_PATH) |
| reportToAggregator | boolean | – | Whether to report gaps to ADR Aggregator |
| scanDirectories | array | – | Specific directories to scan (defaults to src, lib, app, packages) |
No output schema declared.
No examples provided.
analyze_project_ecosystem ~208
Comprehensive recursive project ecosystem analysis with advanced prompting techniques (Knowledge Generation + Reflexion)
| Name | Type | Req | Description |
|---|---|---|---|
| analysisDepth | string | – | Depth of ecosystem analysis |
| analysisScope | array | – | Specific analysis areas to focus on (e.g., ["security", "performance", "architecture", "dependencies"]) |
| enhancedMode | boolean | – | Enable advanced prompting features (Knowledge Generation + Reflexion) |
| includeEnvironment | boolean | – | Automatically include comprehensive environment analysis (default: true) |
| includePatterns | array | – | File patterns to include in analysis |
| knowledgeEnhancement | boolean | – | Enable Knowledge Generation for technology-specific insights |
| learningEnabled | boolean | – | Enable Reflexion learning from past analysis outcomes |
| projectPath | string | – | Path to the project directory to analyze (optional, uses configured PROJECT_PATH if not provided) |
| recursiveDepth | string | – | Depth of recursive project analysis |
| technologyFocus | array | – | Specific technologies to focus analysis on (auto-detected if not provided) |
No output schema declared.
No examples provided.
apply_basic_content_masking ~45
Apply basic content masking (fallback when AI is not available)
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content to mask |
| maskingStrategy | string | – | Strategy for masking content |
No output schema declared.
No examples provided.
bootstrap_validation_loop ~492
**GUIDED EXECUTION MODE**: This tool guides you through an interactive, step-by-step deployment validation workflow. It does NOT execute commands internally - instead, it tells YOU what commands to run and processes the results iteratively. **Workflow**: (1) First call with iteration=0: Detects platform (OpenShift/K8s/Docker), validates environment connection, and requests human approval for target platform. (2) Subsequent calls: After running each command and reporting back with output, the tool provides next steps. **Environment Validation**: Before deployment, the tool verifies connection to the target platform (e.g., `oc status` for OpenShift, `kubectl cluster-info` for K8s) and requires explicit human confirmation. **Validated Patterns Integration**: Automatically identifies base code repositories (e.g., validatedpatterns/common for OpenShift) and guides you to merge them into your project. **Deployment Cleanup**: Supports CI/CD-style workflows with deployment teardown/restart guidance. **Call this tool iteratively**, passing previous command output back each time.
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory where ADRs are stored |
| appSelector | string | – | Label selector scoping every destructive teardown command, e.g. "app=checkout-api". Required before any kubectl/oc delete is offered — the tool will not guess a selector, and without this it returns… |
| autoFix | boolean | – | Whether to generate auto-fix suggestions in guidance |
| currentIteration | number | – | Current iteration number (0 for initial call, then increment). Used to track workflow progress. |
| deploymentCleanupRequested | boolean | – | Set to true to request deployment cleanup/teardown guidance (for CI/CD workflows that need to delete and restart deployments). |
| maxIterations | number | – | Maximum validation/fix iterations |
| previousExecutionOutput | string | – | Output from the previous command execution. Paste the stdout/stderr from running the command that was recommended in the previous iteration. |
| previousExecutionSuccess | boolean | – | Whether the previous command execution succeeded (exit code 0). Set to true if command succeeded, false if it failed. |
| projectPath | string | – | Path to the project directory |
| targetEnvironment | string | – | Target deployment environment |
| updateAdrsWithLearnings | boolean | – | Update ADRs with deployment learnings (non-sensitive) |
No output schema declared.
No examples provided.
compare_adr_progress ~219
Compare TODO.md progress against ADRs and current environment to validate implementation status
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| deepCodeAnalysis | boolean | – | Perform deep code analysis to distinguish mock from production implementations |
| environment | string | – | Target environment context for validation (auto-detect will infer from project structure) |
| environmentConfig | object | – | Environment-specific configuration and requirements |
| environmentValidation | boolean | – | Enable environment-specific validation rules and checks |
| functionalValidation | boolean | – | Validate that code actually functions according to ADR goals, not just exists |
| includeFileChecks | boolean | – | Include file existence and implementation checks |
| includeRuleValidation | boolean | – | Include architectural rule compliance validation |
| projectPath | string | – | Path to project root for environment analysis |
| strictMode | boolean | – | Enable strict validation mode with reality-check mechanisms against overconfident assessments |
| todoPath | string | – | Path to TODO.md file to analyze |
| validationType | string | – | Type of validation to perform |
No output schema declared.
No examples provided.
configure_custom_patterns ~42
Configure custom sensitive patterns for a project
| Name | Type | Req | Description |
|---|---|---|---|
| existingPatterns | array | – | Existing patterns to consider |
| projectPath | string | yes | Path to the project directory |
No output schema declared.
No examples provided.
configure_output_masking ~63
Configure content masking for all MCP outputs
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Configuration action |
| customPatterns | array | – | Custom patterns to mask |
| enabled | boolean | – | Enable or disable output masking |
| strategy | string | – | Masking strategy to use |
No output schema declared.
No examples provided.
create_research_template ~51
Create a research template file for documenting findings
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Research category |
| researchPath | string | – | Path to research directory |
| title | string | yes | Title of the research |
No output schema declared.
No examples provided.
create_rule_set ~106
Create machine-readable rule set in JSON/YAML format
| Name | Type | Req | Description |
|---|---|---|---|
| adrRules | array | – | Rules extracted from ADRs |
| author | string | – | Author of the rule set |
| description | string | – | Description of the rule set |
| name | string | yes | Name of the rule set |
| outputFormat | string | – | Output format for rule set |
| patternRules | array | – | Rules generated from code patterns |
| rules | array | – | Additional rules to include |
No output schema declared.
No examples provided.
deployment_readiness ~411
Comprehensive deployment readiness validation with test failure tracking, deployment history analysis, and hard blocking for unsafe deployments. Integrates with smart_git_push for deployment gating.
| Name | Type | Req | Description |
|---|---|---|---|
| allowMockCode | boolean | – | Allow mock code in deployment (NOT RECOMMENDED) |
| approvalRequired | boolean | – | Require approval for overrides |
| blockOnFailingTests | boolean | – | Block deployment if tests are failing |
| blockOnRecentFailures | boolean | – | Block if recent deployments failed |
| businessJustification | string | – | Business justification for overrides (required for emergency_override) |
| deploymentSuccessThreshold | number | – | Minimum deployment success rate required (%) |
| emergencyBypass | boolean | – | Emergency bypass for critical fixes |
| enableMemoryIntegration | boolean | – | Enable memory entity storage for deployment assessment tracking and historical analysis |
| integrateTodoTasks | boolean | – | Auto-create blocking tasks for issues |
| maxRecentFailures | number | – | Maximum recent deployment failures allowed |
| maxTestFailures | number | – | Maximum test failures allowed (0 = zero tolerance) |
| migrateExistingHistory | boolean | – | Migrate existing JSON-based deployment history to memory entities |
| mockCodeMaxAllowed | number | – | Maximum mock code indicators allowed |
| operation | string | yes | Type of deployment readiness check to perform |
| productionCodeThreshold | number | – | Minimum production code quality score (0-100) |
| projectPath | string | – | Path to project directory (defaults to current working directory) |
| requireAdrCompliance | boolean | – | Require ADR compliance validation |
| requireTestCoverage | number | – | Minimum test coverage percentage required |
| rollbackFrequencyThreshold | number | – | Maximum rollback frequency allowed (%) |
| strictMode | boolean | – | Enable strict validation (recommended for production) |
| targetEnvironment | string | – | Target deployment environment |
| testSuiteRequired | array | – | Required test suites that must pass |
| triggerSmartGitPush | boolean | – | Trigger smart git push validation |
| updateHealthScoring | boolean | – | Update project health scores |
No output schema declared.
No examples provided.
discover_existing_adrs ~49
Discover and catalog existing ADRs in the project
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory to search for ADRs |
| includeContent | boolean | – | Whether to include ADR content in analysis |
No output schema declared.
No examples provided.
expand_analysis_section ~102
Retrieve full analysis content from tiered responses. Expand entire analysis or specific sections stored in memory. Use this when a tool returns a summary with an expandable ID.
| Name | Type | Req | Description |
|---|---|---|---|
| expandableId | string | yes | ID of the expandable analysis (provided in tiered response) |
| format | string | – | Output format (default: markdown) |
| section | string | – | Optional: Specific section to expand (omit to get full analysis). Available sections are listed in the tiered response. |
No output schema declared.
No examples provided.
expand_memory ~74
Phase 3: Retrieve and expand stored content from a tiered response using its expandable ID
| Name | Type | Req | Description |
|---|---|---|---|
| expandableId | string | yes | Expandable ID from a tiered response |
| includeContext | boolean | – | Include related conversation context and session/tool-usage state |
| section | string | – | Optional: specific section to expand |
No output schema declared.
No examples provided.
generate_adr_bootstrap ~203
Generate bootstrap.sh and validate_bootstrap.sh scripts to ensure deployed code follows ADR requirements. **CRITICAL**: Before generating scripts, use WebFetch to query the base code repository (e.g., https://github.com/validatedpatterns/common for OpenShift) and authoritative pattern documentation (e.g., https://play.validatedpatterns.io/). Merge the base repository code into your project and have bootstrap.sh call the pattern's scripts rather than generating everything from scratch. This ensures compliance with validated deployment patterns.
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory where ADRs are stored |
| customValidations | array | – | Custom validation commands to include |
| includeDeployment | boolean | – | Include deployment steps in bootstrap |
| includeTests | boolean | – | Include test execution in bootstrap |
| outputPath | string | – | Directory where to generate scripts |
| projectPath | string | – | Path to the project directory |
| scriptType | string | – | Which scripts to generate |
No output schema declared.
No examples provided.
generate_adr_from_decision ~92
Generate a complete ADR from decision data. TIP: Reference @.mcp-server-context.md to align with existing architectural patterns and decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory where ADRs are stored |
| decisionData | object | yes | – |
| existingAdrs | array | – | List of existing ADRs for numbering and references |
| templateFormat | string | – | ADR template format to use |
No output schema declared.
No examples provided.
generate_adr_todo ~229
Generate TODO.md from ADRs with comprehensive task breakdown. Decomposes each ADR into paired test+production tasks (TDD), links tasks to release milestones, and preserves manual edits via a bounded HTML-comment section. Re-runs are idempotent; tasks for deleted/superseded ADRs move to a Stale Tasks section.
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files (relative to projectPath) |
| dryRun | boolean | – | Compute changes but do not write TODO.md (preview only) |
| linkToMilestones | boolean | – | Link generated tasks to release milestones (local + GitHub merged) |
| phase | string | – | TDD pairing — "both" emits paired test+production tasks (default), "production" or "test" narrows output |
| projectPath | string | – | Project root path (defaults to current working directory) |
| scope | string | – | Which ADRs to decompose: all, pending (proposed/draft), or accepted only |
| todoPath | string | – | Output TODO file (relative to projectPath) |
No output schema declared.
No examples provided.
generate_adrs_from_prd ~137
Generate Architectural Decision Records from a Product Requirements Document with advanced prompting techniques (APE + Knowledge Generation)
| Name | Type | Req | Description |
|---|---|---|---|
| enhancedMode | boolean | – | Enable advanced prompting features (APE + Knowledge Generation) |
| knowledgeEnhancement | boolean | – | Enable Knowledge Generation for domain-specific insights |
| outputDirectory | string | – | Directory to output generated ADRs (optional, uses configured ADR_DIRECTORY if not provided) |
| prdPath | string | yes | Path to the PRD.md file |
| prdType | string | – | Type of PRD for optimized knowledge generation |
| promptOptimization | boolean | – | Enable Automatic Prompt Engineering for optimized ADR generation |
No output schema declared.
No examples provided.
generate_content_masking ~54
Generate masking instructions for detected sensitive content
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Content to mask |
| detectedItems | array | yes | Detected sensitive items to mask |
| maskingStrategy | string | – | Strategy for masking content |
No output schema declared.
No examples provided.
generate_deployment_guidance ~163
Generate deployment guidance and instructions from ADRs with environment-specific configurations
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| customRequirements | array | – | Additional custom requirements |
| environment | string | – | Target deployment environment |
| format | string | – | Output format for guidance |
| generateFiles | boolean | – | Actually generate files (vs just guidance) |
| includeConfigs | boolean | – | Generate configuration files |
| includeRollback | boolean | – | Include rollback procedures |
| includeScripts | boolean | – | Generate deployment scripts |
| includeValidation | boolean | – | Include validation and health checks |
| projectPath | string | – | Project root path (optional, uses configured PROJECT_PATH if not provided) |
| technologyFilter | array | – | Filter by specific technology categories |
No output schema declared.
No examples provided.
generate_research_questions ~145
Generate context-aware research questions and create research tracking system
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| analysisType | string | – | Type of research analysis to perform |
| currentProgress | array | – | Current research progress |
| knowledgeGraph | object | – | Project session state (intents, tool usage, ADR registrations) |
| problems | array | – | Problems to correlate with project session/tool-usage state |
| projectPath | string | – | Path to project directory |
| relevantKnowledge | object | – | Relevant knowledge for question generation |
| researchContext | object | – | Research context and objectives |
| researchQuestions | array | – | Research questions for task tracking |
No output schema declared.
No examples provided.
generate_rules ~80
Generate architectural rules from ADRs and code patterns
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| existingRules | array | – | Existing rules to avoid duplication |
| outputFormat | string | – | Output format for rules |
| projectPath | string | – | Path to project for pattern analysis |
| source | string | – | Source for rule generation |
No output schema declared.
No examples provided.
get_adr_context ~144
Fetch ADR context from ADR Aggregator including summaries, diagrams, timeline data, and code links. Useful for getting a consolidated view of architectural decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| graph_depth | number | – | Knowledge graph depth (Team tier) |
| include_code_links | boolean | – | Include code links (Pro+ tier) |
| include_diagrams | boolean | – | Include Mermaid diagrams (Pro+ tier) |
| include_research | boolean | – | Include research context (Pro+ tier) |
| include_timeline | boolean | – | Include timeline data |
| projectPath | string | – | Project path (defaults to PROJECT_PATH) |
| staleness_filter | string | – | Filter by staleness level |
No output schema declared.
No examples provided.
get_adr_diagrams ~68
Get Mermaid diagrams for ADRs from ADR Aggregator. Includes workflow, relationship, and impact diagrams. Requires Pro+ tier.
| Name | Type | Req | Description |
|---|---|---|---|
| adr_path | string | – | Specific ADR path (returns all if not specified) |
| projectPath | string | – | Project path (defaults to PROJECT_PATH) |
No output schema declared.
No examples provided.
get_adr_priorities ~70
Get ADR priorities for roadmap and backlog planning from ADR Aggregator. Returns prioritized ADRs with scores, dependencies, blockers, implementation status, and gap counts.
| Name | Type | Req | Description |
|---|---|---|---|
| include_ai | boolean | – | Include AI-based priority recommendations |
| projectPath | string | – | Project path (defaults to PROJECT_PATH) |
No output schema declared.
No examples provided.
get_adr_templates ~65
Get domain-specific ADR templates and anti-patterns from ADR Aggregator. Includes best practices for web applications, microservices, APIs, and more. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Domain filter (web_application, microservices, api, data_platform, etc.) |
No output schema declared.
No examples provided.
get_architectural_context ~76
Get detailed architectural context for specific files or the entire project, automatically sets up ADR infrastructure if missing, and provides outcome-focused workflow for project success
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | Specific file path to analyze (optional, analyzes entire project if not provided) |
| includeCompliance | boolean | – | Include compliance checks in the analysis |
No output schema declared.
No examples provided.
get_conversation_snapshot ~40
Phase 3: Get current conversation context snapshot for resumption or analysis
| Name | Type | Req | Description |
|---|---|---|---|
| recentTurnCount | number | – | Number of recent turns to include |
No output schema declared.
No examples provided.
get_development_guidance ~172
Get comprehensive development guidance that translates architectural decisions and workflow recommendations into specific coding tasks, implementation patterns, and development roadmap
| Name | Type | Req | Description |
|---|---|---|---|
| adrsToImplement | array | – | List of ADR titles or file paths that need to be implemented in code |
| currentProgress | string | – | What has already been implemented or current state of development |
| developmentPhase | string | yes | Current development phase |
| focusAreas | array | – | Specific areas to focus on (e.g., ["API design", "database schema", "testing strategy", "deployment pipeline"]) |
| teamContext | object | – | – |
| technologyStack | array | – | Current technology stack (e.g., ["TypeScript", "React", "Node.js", "PostgreSQL", "Docker"]) |
| timeline | string | – | Development timeline or deadline constraints |
No output schema declared.
No examples provided.
get_gaps ~73
Get current code gaps from ADR Aggregator. Returns gaps with their status (open, dismissed, resolved) for tracking and management.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDismissed | boolean | – | Include dismissed gaps |
| includeResolved | boolean | – | Include resolved gaps |
| projectPath | string | – | Project path (defaults to PROJECT_PATH) |
No output schema declared.
No examples provided.
get_knowledge_graph ~76
Get cross-repository knowledge graph from ADR Aggregator with analytics and insights. Visualize ADR relationships across repositories. Requires Team tier.
| Name | Type | Req | Description |
|---|---|---|---|
| include_analytics | boolean | – | Include graph analytics and insights |
| projectPath | string | – | Project path (defaults to PROJECT_PATH) |
| scope | string | – | Scope of the graph |
No output schema declared.
No examples provided.
get_memory_stats ~20
Phase 3: Get statistics about stored conversation memory
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_server_context ~110
Generate a comprehensive context file showing the server's current state, memory, and capabilities. Creates .mcp-server-context.md that can be @ referenced in conversations for instant LLM awareness
| Name | Type | Req | Description |
|---|---|---|---|
| includeDetailed | boolean | – | Include detailed information |
| maxRecentItems | number | – | Maximum number of recent items to show |
| outputPath | string | – | Custom output path for the context file |
| writeToFile | boolean | – | Whether to write the context to .mcp-server-context.md file |
No output schema declared.
No examples provided.
get_staleness_report ~67
Get ADR staleness report from ADR Aggregator with review compliance metrics. Identifies stale ADRs that need attention and provides governance insights.
| Name | Type | Req | Description |
|---|---|---|---|
| projectPath | string | – | Project path (defaults to PROJECT_PATH) |
| threshold | number | – | Days threshold for staleness |
No output schema declared.
No examples provided.
get_workflow_guidance ~190
Get intelligent workflow guidance and tool recommendations based on your goals and project context to achieve expected outcomes efficiently
| Name | Type | Req | Description |
|---|---|---|---|
| availableAssets | array | – | What assets you already have (e.g., ["PRD.md", "existing ADRs", "codebase", "documentation", "test suite"]) |
| goal | string | yes | What you want to accomplish (e.g., "analyze new project", "document existing decisions", "security audit", "modernize legacy system") |
| primaryConcerns | array | – | Main areas of concern (e.g., ["security", "performance", "maintainability", "scalability", "compliance"]) |
| projectContext | string | yes | Current state of your project (e.g., "new project", "existing project with ADRs", "legacy codebase", "greenfield development") |
| timeframe | string | – | Available time/effort level |
No output schema declared.
No examples provided.
incorporate_research ~121
Incorporate research findings into architectural decisions
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Path to ADR directory |
| adrId | string | – | ADR ID for update generation |
| analysisType | string | – | Type of research analysis to perform |
| existingTopics | array | – | Previously identified research topics |
| researchFindings | array | – | Research findings for update generation |
| researchPath | string | – | Path to research directory |
| researchTopics | array | – | Research topics for impact evaluation |
| updateType | string | – | Type of ADR update to generate |
No output schema declared.
No examples provided.
interactive_adr_planning ~145
Interactive guided ADR planning and creation tool - walks users through structured decision-making process with research integration, option evaluation, and automatic ADR generation. TIP: Start by reading @.mcp-server-context.md to understand project context and previous decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| autoResearch | boolean | – | Automatically trigger research when needed |
| generateTodos | boolean | – | Automatically generate TODO items from decisions |
| input | string | – | User input for the current phase (varies by phase) |
| operation | string | yes | Interactive planning operation to perform |
| projectPath | string | yes | Project root path |
| sessionId | string | – | Planning session ID (required for all operations except start_session) |
No output schema declared.
No examples provided.
manage_cache ~47
Manage MCP resource cache (clear, stats, cleanup)
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Cache management action to perform |
| key | string | – | Specific cache key to invalidate (for invalidate action) |
No output schema declared.
No examples provided.
mcp_planning ~399
Enhanced project planning and workflow management tool - phase-based project management, team resource allocation, progress tracking, risk analysis, and executive reporting
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Management action (for manage_phases/manage_resources operations) |
| allocationData | object | – | Resource allocation data |
| analysisType | string | – | Type of risk analysis |
| description | string | – | Project description (for create_project operation) |
| format | string | – | Report output format |
| generateMitigation | boolean | – | Generate mitigation strategies |
| importFromAdrs | boolean | – | Import phases from existing ADRs (for create_project operation) |
| importFromTodos | boolean | – | Import tasks from TODO system (for create_project operation) |
| includeAdrRisks | boolean | – | Analyze risks from ADR complexity |
| includeCharts | boolean | – | Include progress charts and graphs |
| includeDependencyRisks | boolean | – | Analyze dependency chain risks |
| includeResourceRisks | boolean | – | Analyze resource allocation risks |
| includeVisuals | boolean | – | Include visual progress indicators |
| memberData | object | – | Team member data for resource operations |
| memberId | string | – | Team member ID for resource operations |
| operation | string | yes | Project planning operation to perform |
| phaseData | object | – | Phase data for create/update operations |
| phaseId | string | – | Phase ID for phase operations |
| phases | array | – | Initial project phases (for create_project operation) |
| projectName | string | – | Project name (for create_project operation) |
| projectPath | string | yes | Project root path |
| reportType | string | – | Type of progress report or generated report |
| targetStatus | string | – | Target status for phase transition |
| team | array | – | Team structure (for create_project operation) |
| timeframe | string | – | Time frame for reports and tracking |
| updateTaskProgress | boolean | – | Sync progress from TODO system |
No output schema declared.
No examples provided.
memory_loading ~115
Advanced memory loading tool for the memory-centric architecture. Query, explore, and manage memory entities and relationships. Load ADRs into memory system and perform intelligent queries.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Memory operation to perform |
| entityId | string | – | Entity ID for get_entity and find_related actions |
| forceReload | boolean | – | Force reload of ADRs (load_adrs action) |
| maxDepth | number | – | Maximum depth for relationship traversal (find_related action) |
| query | object | – | Query parameters for entity search |
No output schema declared.
No examples provided.
perform_research ~139
Perform research using cascading sources: project files → session/tool-usage tracker → environment resources → web search (fallback)
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| confidenceThreshold | number | – | Minimum confidence threshold (0-1) before suggesting web search |
| performWebSearch | boolean | – | Enable web search recommendations when confidence is low |
| projectPath | string | – | Path to project directory |
| question | string | yes | The research question to answer |
| researchDirectory | string | – | Directory the research document is written to. Previously unset and unsettable: output went to docs/context/research/ regardless (#1528). |
No output schema declared.
No examples provided.
query_conversation_history ~87
Phase 3: Search and retrieve conversation sessions based on filters
| Name | Type | Req | Description |
|---|---|---|---|
| dateRange | object | – | Filter by date range |
| keyword | string | – | Search keyword in conversation turns |
| limit | number | – | Maximum number of sessions to return |
| projectPath | string | – | Filter by project path |
| toolsUsed | array | – | Filter by tools used in the session |
No output schema declared.
No examples provided.
release_tracking ~397
Track releases mapped to ADR decisions. Generates changelogs, manages milestones, compares releases, and assesses release readiness. Supports greenfield and brownfield projects. Writes CHANGELOG.md, creates GitHub Releases and Milestones.
| Name | Type | Req | Description |
|---|---|---|---|
| compareFrom | string | – | Starting version for comparison |
| compareTo | string | – | Ending version for comparison |
| createGithubRelease | boolean | – | Create a GitHub Release (requires gh CLI) |
| format | string | – | Changelog output format |
| groupByAdr | boolean | – | Group changelog entries by ADR |
| includeAdrLinks | boolean | – | Include ADR references in changelog |
| includeCommitHashes | boolean | – | Include commit hashes in output |
| includeReadiness | boolean | – | Include release readiness score |
| includeTimeline | boolean | – | Include mermaid timeline diagram |
| localOnly | boolean | – | For create_milestone: persist locally instead of calling gh CLI. Useful when gh auth is unavailable. |
| milestoneDescription | string | – | GitHub milestone description |
| milestoneDueDate | string | – | Milestone due date (YYYY-MM-DD) |
| milestoneTitle | string | – | GitHub milestone title (for create_milestone) |
| operation | string | yes | Operation to perform |
| projectPath | string | – | Project root path (defaults to current working directory) |
| releasePlanPath | string | – | Path to RELEASE_PLAN.md (relative to projectPath). |
| syncGithubMilestones | boolean | – | Sync milestones to GitHub (requires gh CLI) |
| updateTodo | boolean | – | Update TODO.md with milestone status |
| version | string | – | Release version to track (e.g., v2.3.0) |
| writeReleasePlan | boolean | – | For create_milestone/push_local_milestones: also render local milestones into RELEASE_PLAN.md (bounded section). |
| writeToFile | boolean | – | Write CHANGELOG.md to repo |
No output schema declared.
No examples provided.
request_action_confirmation ~55
Request confirmation before applying research-based changes
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Description of the action to be performed |
| details | string | yes | Detailed information about the action |
| impact | string | – | Impact level of the action |
No output schema declared.
No examples provided.
review_existing_adrs ~138
Review existing ADRs against actual code implementation with cloud/DevOps expertise. TIP: After review, call get_server_context to update @.mcp-server-context.md with findings.
| Name | Type | Req | Description |
|---|---|---|---|
| adrDirectory | string | – | Directory containing ADR files |
| analysisDepth | string | – | Depth of analysis to perform |
| generateUpdatePlan | boolean | – | Generate action plan for updating non-compliant ADRs |
| includeTreeSitter | boolean | – | Use tree-sitter for enhanced code analysis |
| projectPath | string | – | Path to the project directory |
| specificAdr | string | – | Specific ADR filename or title to review (optional) |
No output schema declared.
No examples provided.
search_codebase ~151
Atomic tool for searching codebase files based on query patterns. Returns raw file matches with relevance scores. Extracted from ResearchOrchestrator per ADR-018.
| Name | Type | Req | Description |
|---|---|---|---|
| enableTreeSitter | boolean | – | Use tree-sitter for enhanced analysis |
| includeContent | boolean | – | Include file content in results |
| maxFiles | number | – | Maximum files to return |
| projectPath | string | – | Path to project root |
| query | string | yes | Search query (e.g., "Docker configuration", "authentication") |
| relevanceThreshold | number | – | Minimum relevance threshold (0-1) |
| scope | array | – | Optional file scope patterns (e.g., ["src/**", "config/**"]) |
No output schema declared.
No examples provided.
set_project_path ~96
Dynamically set the active project path for the current session. Call this at the start of a session to switch between projects without restarting the server or modifying environment variables. All subsequent tool calls will use this path as the default.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the project directory. Must be an existing directory. |
| validatePath | boolean | – | Whether to validate that the path exists and is a directory (default: true) |
No output schema declared.
No examples provided.
How do I install the io.github.tosin2013/mcp-adr-analysis-server server?
io.github.tosin2013/mcp-adr-analysis-server runs locally as an npm package, launched with npx -y mcp-adr-analysis-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-adr-analysis-server
claude mcp add tosin2013-mcp-adr-analysis-server -- npx -y mcp-adr-analysis-server
What is the io.github.tosin2013/mcp-adr-analysis-server server?
io.github.tosin2013/mcp-adr-analysis-server is listed in the public MCP registry as io.github.tosin2013/mcp-adr-analysis-server. ADR drift detection, content safety, and decision memory for architectural decisions. This page covers its npm package (mcp-adr-analysis-server).
Is the io.github.tosin2013/mcp-adr-analysis-server server safe to use?
io.github.tosin2013/mcp-adr-analysis-server scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.tosin2013/mcp-adr-analysis-server server expose?
io.github.tosin2013/mcp-adr-analysis-server exposes 63 tools: analyze_project_ecosystem, get_architectural_context, generate_adrs_from_prd, compare_adr_progress, analyze_content_security, and 58 more. Their descriptions and schemas cost roughly 8,644 tokens of context every time the server is loaded.
Is the io.github.tosin2013/mcp-adr-analysis-server server still maintained?
io.github.tosin2013/mcp-adr-analysis-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.tosin2013/mcp-adr-analysis-server server under?
io.github.tosin2013/mcp-adr-analysis-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.