fedramp-20x-mcp 0.4.9

MCP server for querying FedRAMP 20x requirements

FedRAMP 20x MCP Server

An MCP (Model Context Protocol) server that provides access to FedRAMP 20x security requirements and controls with Azure-first guidance.

Overview

This server loads FedRAMP 20x data from the official FedRAMP documentation repository and provides tools for querying requirements by control, family, or keyword.

Data Sources:

• Requirements Data: JSON files from github.com/FedRAMP/docs/tree/main/data
• Documentation: Markdown files from github.com/FedRAMP/docs/tree/main/docs

Azure Focus: All implementation examples, architecture patterns, and vendor recommendations prioritize Microsoft Azure services (Azure Government, Microsoft Entra ID, Azure Key Vault, AKS, Azure Functions, Bicep, etc.) while remaining cloud-agnostic where appropriate.

Complete Data Coverage

The server provides access to 329 requirements across all 12 FedRAMP 20x documents:

• ADS - Authorization Data Sharing (22 requirements)
• CCM - Collaborative Continuous Monitoring (25 requirements)
• FRD - FedRAMP Definitions (50 definitions)
• FSI - FedRAMP Security Inbox (16 requirements)
• ICP - Incident Communications Procedures (9 requirements)
• KSI - Key Security Indicators (72 indicators)
• MAS - Minimum Assessment Scope (12 requirements)
• PVA - Persistent Validation and Assessment (22 requirements)
• RSC - Recommended Secure Configuration (10 requirements)
• SCN - Significant Change Notifications (26 requirements)
• UCM - Using Cryptographic Modules (4 requirements)
• VDR - Vulnerability Detection and Response (59 requirements)

Features

• Query by Control: Get detailed information about specific FedRAMP requirements
• Query by Family: List all requirements within a family
• Keyword Search: Search across all requirements using keywords
• FedRAMP Definitions: Look up official FedRAMP term definitions
• Key Security Indicators: Access and query FedRAMP Key Security Indicators (KSI)
• Documentation Search: Search and retrieve official FedRAMP documentation markdown files
• Dynamic Content: Automatically discovers and loads all markdown documentation files
• Implementation Planning: Generate strategic interview questions to help product managers and engineers think through FedRAMP 20x implementation considerations

Important Clarification: OSCAL Format FedRAMP 20x requires machine-readable formats (JSON, XML, or structured data) for Authorization Data Sharing. OSCAL is NOT mentioned in FedRAMP 20x requirements - it's a NIST standard that can be used as one potential implementation approach. The actual requirement is simply "machine-readable" - you can use custom JSON/XML or OSCAL based on your implementation needs.

📄 See OSCAL_CLARIFICATION.md for detailed guidance on format requirements and implementation approaches.

Installation

Prerequisites

• Python 3.10 or higher
• pip (included with Python)
• Python must be in your system PATH

Setup

# Clone the repository
git clone https://github.com/KevinRabun/FedRAMP20xMCP.git
cd FedRAMP20xMCP

# Create virtual environment and install
python -m venv .venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
pip install -e .

# If using uv (alternative package manager):
uv pip install -e .

Dependencies:

• mcp>=1.2.0 - Model Context Protocol SDK
• httpx>=0.27.0 - HTTP client for fetching FedRAMP data
• openpyxl>=3.1.0 - Excel file generation for export features
• python-docx>=1.1.0 - Word document generation for KSI specifications

Troubleshooting: If you get "Python was not found" errors:

1. Ensure Python is installed and added to PATH
2. Try using python3 instead of python
3. Or use the full path to python.exe in .vscode/mcp.json

Usage

With VS Code and GitHub Copilot

1. Install the VS Code MCP extension (if not already installed)

2. Configure the MCP server - Choose one of the following scopes:

   Option A: Workspace-level (Recommended for sharing)

   Add to .vscode/mcp.json in your project:

   {
     "servers": {
       "fedramp-20x-mcp": {
         "type": "stdio",
         "command": "python",
         "args": ["-m", "fedramp_20x_mcp"]
       }
     }
   }
   

   If Python is not in PATH, update the command to use your virtual environment's Python:

   {
     "servers": {
       "fedramp-20x-mcp": {
         "type": "stdio",
         "command": "${workspaceFolder}/.venv/Scripts/python.exe",  // Windows
         // "command": "${workspaceFolder}/.venv/bin/python",       // macOS/Linux
         "args": ["-m", "fedramp_20x_mcp"]
       }
     }
   }
   

   Option B: User-level (Global across all projects)

   Add to VS Code User Settings (settings.json):

   {
     "github.copilot.chat.mcp.servers": {
       "fedramp-20x-mcp": {
         "type": "stdio",
         "command": "python",
         "args": ["-m", "fedramp_20x_mcp"]
       }
     }
   }
   

   Security Note: Do NOT use "alwaysAllow" in configuration. VS Code will prompt you to grant permissions on first use, which is a security best practice.

3. Optional: Configure VS Code settings by copying .vscode/settings.json.example to .vscode/settings.json

4. Reload VS Code to activate the MCP server

5. Grant permissions when prompted by VS Code (first use only)

6. Use with GitHub Copilot Chat:

   • Open Copilot Chat
   • Ask questions about FedRAMP 20x requirements
   • Use @workspace to query specific controls or families
   • Access all 24 tools and 9 prompts

With Claude Desktop

Add this server to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "fedramp-20x": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/FedRAMP20xMCP",
        "run",
        "fedramp-20x-mcp"
      ]
    }
  }
}

Note: Replace /absolute/path/to/FedRAMP20xMCP with your actual installation path.

With MCP Inspector

Test the server using the MCP Inspector:

npx @modelcontextprotocol/inspector python -m fedramp_20x_mcp

Recommended MCP Server Setup

For the best FedRAMP 20x compliance workflow, combine this server with other MCP servers that provide Azure and Microsoft context. Here's a complete configuration that includes Azure integration, Microsoft documentation, and GitHub access.

Complete .vscode/mcp.json Configuration

Create or update .vscode/mcp.json in your project with this configuration:

{
  "servers": {
    // FedRAMP 20x Requirements & Documentation
    "fedramp-20x-mcp": {
      "type": "stdio",
      "command": "${workspaceFolder}/.venv/Scripts/python.exe",  // Windows
      // "command": "${workspaceFolder}/.venv/bin/python",       // macOS/Linux
      "args": ["-m", "fedramp_20x_mcp"]
    },
    
    // Azure Resources & Operations (Official Microsoft MCP Server)
    "azure-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@azure/mcp-server-azure"
      ],
      "env": {
        "AZURE_SUBSCRIPTION_ID": "your-subscription-id-here"
      }
    },
    
    // Microsoft Documentation (Learn, Azure Docs, API References)
    "microsoft-docs": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@microsoft/mcp-server-docs"
      ]
    },
    
    // GitHub (for Azure samples, Bicep templates, FedRAMP examples)
    "github": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your-github-token-here"
      }
    }
  }
}

What Each Server Provides

fedramp-20x-mcp (This Server)

• 329 FedRAMP 20x requirements
• 72 Key Security Indicators
• 50 official definitions
• Official markdown documentation files
• Implementation examples and Azure guidance
• Evidence collection automation tools
• Compliance validation tools

azure-mcp (Microsoft Official)

• Query Azure resources (VMs, databases, networks)
• Check Azure Policy compliance
• Review Security Center/Defender alerts
• Validate configurations against FedRAMP requirements
• Real-time Azure resource inventory

microsoft-docs

• Azure service documentation
• API references
• Best practices guides
• Architecture patterns
• Security baselines

github

• Access Azure Quick Start templates
• FedRAMP Bicep/Terraform examples
• Azure sample applications
• Community compliance patterns

Setup Steps

1. Configure Azure Authentication (for azure-mcp):

   # Install Azure CLI if not already installed
   # Login to Azure
   az login
   
   # Set your subscription
   az account set --subscription "your-subscription-id"
   
   # Add subscription ID to mcp.json
   

2. Configure GitHub Token (for github):

   • Go to https://github.com/settings/tokens
   • Create a Personal Access Token with repo scope
   • Add token to mcp.json GITHUB_PERSONAL_ACCESS_TOKEN

3. Reload VS Code to activate all servers

4. Grant Permissions when VS Code prompts (first use)

Example Workflow with Multiple Servers

User: "Check if my Azure Key Vault configuration meets FedRAMP KSI-IAM-06 requirements"

AI Assistant uses:
1. fedramp-20x-mcp → Get KSI-IAM-06 requirements
2. azure-mcp → Query actual Key Vault configuration
3. microsoft-docs → Get Azure Key Vault security best practices
4. Returns compliance analysis with gaps and remediation steps

Simplified Setup (FedRAMP Only)

If you only want FedRAMP requirements without Azure integration:

{
  "servers": {
    "fedramp-20x-mcp": {
      "type": "stdio",
      "command": "${workspaceFolder}/.venv/Scripts/python.exe",
      "args": ["-m", "fedramp_20x_mcp"]
    }
  }
}

Available Tools

The server provides 26 tools organized into the following categories:

Core Tools (8): Query requirements, definitions, and KSIs Documentation Tools (3): Search and retrieve FedRAMP documentation Enhancement Tools (6): Implementation examples, dependencies, effort estimation Export Tools (3): Excel/CSV export and KSI specification generation Planning Tools (1): Generate strategic implementation questions Evidence Collection Automation Tools (3): Infrastructure code, collection code, architecture guidance Implementation Mapping Tools (2): KSI family matrices and step-by-step implementation checklists

get_control

Get detailed information about a specific FedRAMP requirement or control.

Parameters:

• control_id (string): The requirement identifier (e.g., "FRD-ALL-01", "KSI-AFR-01")

list_family_controls

List all requirements within a specific family.

Parameters:

• family (string): The family identifier (e.g., "FRD", "KSI", "MAS")

search_requirements

Search for requirements containing specific keywords.

Parameters:

• keywords (string): Keywords to search for in requirement text

get_definition

Get the FedRAMP definition for a specific term.

Parameters:

• term (string): The term to look up (e.g., "vulnerability", "cloud service offering")

list_definitions

List all FedRAMP definitions with their terms.

Returns: Complete list of all FedRAMP definition terms

search_definitions

Search FedRAMP definitions by keywords.

Parameters:

• keywords (string): Keywords to search for in definitions

get_ksi

Get detailed information about a specific Key Security Indicator.

Parameters:

• ksi_id (string): The KSI identifier (e.g., "KSI-AFR-01")

list_ksi

List all Key Security Indicators.

Returns: Complete list of all Key Security Indicators with their names

compare_with_rev4

Compare FedRAMP 20x with Rev 4/Rev 5 requirements for specific areas.

Parameters:

• requirement_area (string): Area to compare (e.g., "continuous monitoring", "vulnerability management", "authorization boundary", "evidence collection", "change management", "incident response")

get_implementation_examples

Get practical implementation examples for specific requirements.

Parameters:

• requirement_id (string): The requirement identifier (e.g., "KSI-IAM-01", "FRR-VDR-01")

check_requirement_dependencies

Check dependencies between FedRAMP 20x requirements.

Parameters:

• requirement_id (string): The requirement identifier to check dependencies for

estimate_implementation_effort

Estimate implementation effort for specific requirements.

Parameters:

• requirement_id (string): The requirement identifier to estimate effort for

get_cloud_native_guidance

Get cloud-native implementation guidance for specific Azure and multi-cloud technologies.

Parameters:

• technology (string): Technology to get guidance for (e.g., "kubernetes", "containers", "serverless", "terraform")

Note: All cloud examples and best practices prioritize Azure services (AKS, Azure Functions, Key Vault, Bicep, etc.)

validate_architecture

Validate a system architecture against FedRAMP 20x requirements.

Parameters:

• architecture_description (string): Description of the architecture to validate

search_documentation

Search FedRAMP official documentation markdown files for specific keywords.

Parameters:

• keywords (string): Keywords to search for in documentation

Returns: Matching documentation sections with context from all available markdown files

Note: Automatically loads all markdown files from the docs directory, so new documentation is always searchable.

get_documentation_file

Get the full content of a specific FedRAMP documentation file.

Parameters:

• filename (string): The markdown filename (e.g., "overview.md", "key-security-indicators.md")

Returns: Full markdown content of the documentation file

list_documentation_files

List all available FedRAMP documentation files.

Returns: Complete list of all markdown documentation files dynamically discovered from the repository

export_to_excel

Export FedRAMP 20x data to Excel files for offline analysis and reporting.

Parameters:

• export_type (string): Type of data to export:
  • "ksi" - All 72 Key Security Indicators
  • "all_requirements" - All 329 requirements across all families
  • "definitions" - All FedRAMP term definitions
• output_path (string, optional): Custom output path. If not provided, saves to Downloads folder

Returns: Path to the generated Excel file with professional formatting (styled headers, borders, frozen panes)

KSI Export Columns:

1. KSI ID - Unique identifier (e.g., KSI-AFR-01)
2. Name - KSI name
3. Category - Control family category
4. Status - Active or Retired
5. Statement - Full requirement statement
6. Note - Additional information (e.g., supersession notes for retired KSIs)
7. NIST 800-53 Controls - Related security controls with titles
8. Reference - Reference document name (if applicable)
9. Reference URL - Link to FedRAMP documentation (if applicable)
10. Impact Levels - Applicable levels (Low, Moderate, High)

All Requirements Export Columns:

1. Requirement ID - Unique identifier
2. Family - Control family
3. Term/Name - Requirement name
4. Description - Full description
5. Document - Source document

Definitions Export Columns:

1. Term - FedRAMP term
2. Definition - Term definition
3. Notes - Additional context
4. References - Related documentation

Example usage:

• Export all KSIs: export_to_excel("ksi")
• Export all requirements: export_to_excel("all_requirements")
• Export definitions: export_to_excel("definitions")

export_to_csv

Export FedRAMP 20x data to CSV files for data analysis and spreadsheet imports.

Parameters:

• export_type (string): Type of data to export:
  • "ksi" - All 72 Key Security Indicators
  • "all_requirements" - All 329 requirements across all families
  • "definitions" - All FedRAMP term definitions
• output_path (string, optional): Custom output path. If not provided, saves to Downloads folder

Returns: Path to the generated CSV file

Columns: Same structure as Excel export (see above for detailed column descriptions)

Example usage:

• Export all KSIs: export_to_csv("ksi")
• Export all requirements: export_to_csv("all_requirements")
• Export definitions: export_to_csv("definitions")

generate_ksi_specification

Generate a comprehensive product specification Word document for a KSI to guide engineering implementation and planning.

Parameters:

• ksi_id (string): The KSI identifier (e.g., "KSI-AFR-01")
• evidence_collection_strategy (string): High-level evidence collection strategy description provided by the user
• output_path (string, optional): Custom output path. If not provided, saves to Downloads folder

Returns: Path to the generated Word (.docx) document

Document Contents:

• Metadata: KSI ID, category, impact levels, status, date
• Overview: Purpose and scope aligned with FedRAMP 20x
• Requirement Statement: Full KSI requirement text
• NIST 800-53 Controls: Related security controls with titles
• Azure-First Implementation: Recommended Azure services, IaC guidance, automation strategies
• Evidence Collection: User-defined strategy + recommended evidence types and flexible collection schedule
• 5-Phase Implementation Plan: Requirements analysis → Design → Implementation → Testing → Documentation (engineering teams determine timelines)
• Team Roles: Cloud architect, DevOps, security engineer, compliance specialist, etc.
• Success Criteria: Measurable outcomes for implementation validation
• Risks and Mitigation: Common risks with Azure-specific mitigation strategies
• Resources: Links to FedRAMP, NIST, Azure documentation

Azure Services Recommended (context-aware based on KSI category):

• Microsoft Entra ID, Azure Policy, Azure Monitor (all KSIs)
• Microsoft Defender for Cloud, Azure Key Vault, Azure Firewall (category-specific)
• Microsoft Sentinel, Azure Automation, Log Analytics (control-specific)

Example usage:

Generate specification for KSI-AFR-01:
> generate_ksi_specification with ksi_id="KSI-AFR-01" 
  and evidence_collection_strategy="Collect Azure Policy compliance reports quarterly using Azure Automation runbooks. Store evidence in Azure Blob Storage with immutable storage policy."

generate_implementation_questions

Generate strategic interview questions for product managers and engineers to facilitate thoughtful planning discussions.

Parameters:

• requirement_id (string): The requirement or KSI identifier (e.g., "FRR-CCM-01", "KSI-IAM-01")

Returns: Comprehensive set of strategic questions organized by stakeholder role

Question Categories:

1. Strategic Questions for Product Managers (10 questions):

   • Business Impact & ROI
   • Customer Value & Competitive Position
   • Resource Allocation & Prioritization
   • Dependencies & Phasing
   • Cost-Benefit Analysis

2. Technical Questions for Engineers (15 questions):

   • Architecture & Design Decisions
   • Azure Service Selection
   • Automation Opportunities
   • Monitoring & Evidence Collection
   • Operations & Maintenance

3. Cross-Functional Questions (10 questions):

   • Security & Compliance Integration
   • User Experience Impact
   • Training & Support Needs
   • Incident Response Alignment

4. Azure-Specific Considerations (dynamic, up to 20 questions):

   • Microsoft Entra ID configuration
   • Azure RBAC and Conditional Access
   • Log Analytics and Sentinel integration
   • Azure Policy and governance
   • Defender for Cloud setup
   • Key Vault and encryption strategy

Additional Guidance:

• Decision Framework (5 must-answer questions before implementation)
• Success Criteria (5 measurable outcomes)
• Red Flags (5 warning signs to watch for)
• Next Steps (9-phase implementation approach)
• Recommended Resources (Microsoft docs, FedRAMP resources, community)

Purpose: Help teams think deeply about implementation considerations, trade-offs, and success criteria before committing resources. Questions are designed to facilitate planning sessions, design reviews, and stakeholder alignment.

get_infrastructure_code_for_ksi

Generate Infrastructure as Code templates (Bicep or Terraform) for automated evidence collection infrastructure.

Parameters:

• ksi_id (string): The Key Security Indicator identifier (e.g., "KSI-IAM-01", "KSI-MLA-01")
• infrastructure_type (string): Either "bicep" or "terraform"

Returns: Complete IaC templates for deploying evidence collection infrastructure

Supported KSI Families:

• IAM (Identity and Access Management): Microsoft Entra ID, Log Analytics workspaces, diagnostic settings, automation accounts
• MLA (Monitoring, Logging, and Auditing): Log Analytics workspaces, Azure Sentinel, diagnostic settings, alert rules
• AFR (Audit and Financial Reporting): Storage accounts with immutability, event subscriptions, audit logs
• CNA (Change Notification and Approval): Event Grid topics, Logic Apps, DevOps pipelines, change tracking
• RPL (Release Pipeline): Azure DevOps pipelines, deployment slots, rollback capabilities, approval gates
• SVC (Service and Vulnerability Management): Defender for Cloud, security assessments, compliance dashboards

Example Usage:

> get_infrastructure_code_for_ksi with ksi_id="KSI-IAM-01" and infrastructure_type="bicep"

Output Includes:

• Azure resource definitions (Log Analytics, Storage, Event Grid, etc.)
• Diagnostic settings for evidence collection
• Retention policies and immutability
• Integration with Azure Monitor and Sentinel
• Automation for evidence gathering
• RBAC roles and permissions

get_evidence_collection_code

Generate business logic code (Python, C#, or PowerShell) for collecting and storing KSI evidence programmatically.

Parameters:

• ksi_id (string): The Key Security Indicator identifier (e.g., "KSI-IAM-01")
• language (string): Either "python", "csharp", or "powershell"

Returns: Complete code examples with authentication, evidence collection, and storage

Code Features:

• Authentication: Azure DefaultAzureCredential pattern for managed identity or local development
• Evidence Collection: SDKs for Microsoft Graph API, Azure Resource Manager, Azure Monitor
• Evidence Storage: Save to Azure Blob Storage with immutability and metadata tagging
• Error Handling: Comprehensive try-catch patterns and logging
• Documentation: Inline comments explaining each step

Supported Languages:

• Python: Uses azure-identity, azure-storage-blob, azure-monitor-query, msgraph-sdk
• C#: Uses Azure.Identity, Azure.Storage.Blobs, Azure.Monitor.Query, Microsoft.Graph
• PowerShell: Uses Az.Accounts, Az.Storage, Az.Monitor, Microsoft.Graph modules

Example Usage:

> get_evidence_collection_code with ksi_id="KSI-MLA-01" and language="python"

Output Includes:

• SDK imports and authentication setup
• Evidence collection logic specific to the KSI
• JSON formatting and metadata tagging
• Blob storage upload with immutability
• Error handling and retry logic

get_evidence_automation_architecture

Get comprehensive architecture guidance for automated evidence collection systems.

Parameters:

• scope (string): Architecture scope - "minimal", "single-ksi", "category", or "all"

Returns: Complete architecture patterns with components, data flows, and implementation guidance

Architecture Scopes:

1. minimal: Quick-start architecture for pilot projects

   • Single Log Analytics workspace
   • Azure Function for scheduled evidence collection
   • Blob storage with basic retention
   • Event Grid for notifications
   • Estimated ~$100-200/month

2. single-ksi: Production architecture for one KSI

   • Dedicated evidence collection infrastructure
   • Azure Functions with monitoring
   • Managed identities for security
   • Sentinel integration
   • Estimated ~$300-500/month

3. category: Enterprise architecture for one KSI category (IAM, MLA, etc.)

   • Category-specific evidence collectors
   • Centralized evidence storage
   • Automated reporting dashboards
   • Integration with Azure Policy
   • Estimated ~$1,000-2,000/month

4. all: Complete enterprise architecture for all 72 KSIs

   • Multi-region evidence collection
   • High-availability design
   • Automated compliance reporting
   • Integration with GRC tools
   • Estimated ~$5,000-10,000/month

Example Usage:

> get_evidence_automation_architecture with scope="all"

Output Includes:

• Component diagram and descriptions
• Data flow architecture
• Security and identity patterns
• Monitoring and alerting strategy
• Evidence storage and retention
• Disaster recovery considerations
• Integration patterns with Azure services
• Scaling recommendations
• Implementation steps

Available Prompts

The server provides 9 prompts for FedRAMP compliance workflows:

generate_implementation_questions with requirement_id="FRR-CCM-01"

Major Comprehensive Prompts

control_implementation - Detailed guidance for implementing specific NIST 800-53 controls

risk_assessment - Framework for conducting FedRAMP-aligned risk assessments

continuous_monitoring - Guide for establishing continuous monitoring programs

boundary_definition - Help define authorization boundaries and interconnections

Major Comprehensive Prompts

initial_assessment_roadmap - Complete 6-phase roadmap for FedRAMP 20x authorization with checklists, deliverables, and critical success factors (engineering teams determine timelines)

quarterly_review_checklist - Comprehensive checklist for FedRAMP 20x quarterly reviews (FRR-CCM-QR) covering all 72 KSIs, vulnerability review, and change review

api_design_guide - Complete guide for Authorization Data Sharing API (FRR-ADS) with endpoints, authentication, OSCAL formats, and examples

ksi_implementation_priorities - Prioritized guide for implementing all 72 Key Security Indicators across 8 priority phases with dependency mapping (engineering teams determine rollout timelines)

vendor_evaluation - Comprehensive vendor assessment framework with category-specific questions, scorecard template, and evaluation criteria

documentation_generator - OSCAL SSP templates, procedure templates (VDR, ICP, SCN), and KSI implementation documentation templates

migration_from_rev5 - Detailed migration plan from FedRAMP Rev 5 to 20x with 7-phase approach, gap analysis, and requirement mapping (teams determine timelines and budgets)

audit_preparation - Comprehensive guide for FedRAMP 20x assessment preparation with evidence gathering, common findings, and interview prep (teams determine preparation timeline)

azure_ksi_automation - Complete guide for implementing all 72 KSIs using Microsoft, Azure, and M365 capabilities including PowerShell scripts, Azure CLI commands, Microsoft Graph API integration, KQL queries, Azure Functions/Logic Apps, evidence collection framework, and integration with Defender suite, Entra ID, Key Vault, and Sentinel

Data Source

Data is fetched from the official FedRAMP repository: https://github.com/FedRAMP/docs/tree/main/data

Development

Running Tests

The project includes comprehensive test coverage across all functionality:

# Run all tests
pytest

# Run with coverage report
pytest --cov=src --cov-report=html

# Run specific test suites
python tests/test_loader.py                      # Data loading (329 requirements)
python tests/test_definitions.py                 # Definitions & KSIs (50 + 72)
python tests/test_docs_integration.py            # Documentation (15 files)
python tests/test_implementation_questions.py    # Strategic questions
python tests/test_tool_registration.py           # Architecture validation (24 tools)
python tests/test_evidence_automation.py         # IaC generation (Bicep/Terraform/Code)
python tests/test_all_tools.py                   # All tools comprehensive test

Test Coverage:

• ✅ Data Loading: 329 requirements from 12 documents
• ✅ Definitions: 50 FedRAMP terms
• ✅ KSIs: 72 Key Security Indicators
• ✅ Documentation: 15 official FedRAMP markdown files
• ✅ Tool Registration: All 24 tools across 7 modules
• ✅ IaC Generation: Bicep & Terraform templates for IAM, MLA, AFR families
• ✅ Code Generation: Python, C#, PowerShell evidence collection code
• ✅ Template Variations: Family-specific customization validated

Project Structure

FedRAMP20xMCP/
├── src/
│   └── fedramp_20x_mcp/    # Main package
│       ├── __init__.py     # Package initialization
│       ├── __main__.py     # Entry point for python -m
│       ├── server.py       # MCP server entry point (270 lines, 15 prompts)
│       ├── data_loader.py  # FedRAMP data fetching and caching
│       ├── templates/      # Infrastructure & code templates
│       │   ├── __init__.py # Template loader functions
│       │   ├── bicep/      # Bicep IaC templates (7 files)
│       │   ├── terraform/  # Terraform IaC templates (6 files)
│       │   └── code/       # Code generation templates (7 files)
│       ├── prompts/        # Prompt templates (15 files)
│       │   └── __init__.py # Prompt loader function
│       ├── tools/          # Tool modules (24 tools across 7 modules)
│       │   ├── __init__.py # Tool registration system
│       │   ├── requirements.py    # Core requirements tools (3)
│       │   ├── definitions.py     # Definition lookup tools (3)
│       │   ├── ksi.py             # KSI tools (2)
│       │   ├── documentation.py   # Documentation tools (3)
│       │   ├── export.py          # Export tools (3)
│       │   ├── enhancements.py    # Enhancement tools (7)
│       │   └── evidence.py        # Evidence automation tools (3)
│       └── __fedramp_cache__/  # Runtime cache for FedRAMP data
├── tests/                   # Test suite
│   ├── __init__.py
│   ├── test_loader.py      # Data loader tests (329 requirements)
│   ├── test_definitions.py # Definition tool tests (50 definitions, 72 KSIs)
│   ├── test_docs_integration.py  # Documentation integration tests (15 files)
│   ├── test_implementation_questions.py  # Implementation questions tests
│   ├── test_tool_registration.py  # Tool architecture validation (24 tools, 7 modules)
│   ├── test_evidence_automation.py  # IaC generation tests (Bicep/Terraform/Python/C#/PowerShell)
│   └── test_all_tools.py   # Comprehensive tool tests (all 24 tools)
├── .github/
│   ├── workflows/          # CI/CD workflows
│   │   ├── test.yml        # Test workflow (multi-platform)
│   │   ├── publish.yml     # PyPI & MCP Registry publishing
│   │   └── release.yml     # GitHub release workflow
│   └── copilot-instructions.md  # GitHub Copilot context
├── .vscode/
│   ├── mcp.json            # VS Code MCP configuration
│   └── settings.json.example
├── pyproject.toml          # Project metadata and dependencies
├── server.json             # MCP Registry metadata
├── uv.lock                 # UV dependency lock file
├── LICENSE                 # MIT License
├── README.md               # This file
├── CONTRIBUTING.md         # Contribution guidelines
└── .gitignore              # Git exclusions (includes MCP tokens)

Architecture Highlights:

• Modular Design: Tools organized into 7 logical modules by functionality
• Template System: Reusable Bicep/Terraform templates for IaC generation
• Prompt Templates: External prompt files for easy updates without code changes
• Clean Separation: 97.2% reduction in main server.py (9,810 → 270 lines)
• Registration Pattern: Tools use *_impl functions with centralized registration

License

MIT License - see LICENSE file for details.

This project is open source and contributions are welcome! See CONTRIBUTING.md for guidelines.

The FedRAMP data is provided by the U.S. General Services Administration as public domain content.

References

• Model Context Protocol Documentation
• FedRAMP Official Website
• FedRAMP Data Repository