FedRAMP Rules MCP Server
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fedramp_searchA | Full-text search across the FedRAMP Consolidated Rules for 2026 corpus. |
| fedramp_get_documentA | Return the full markdown of one FedRAMP corpus document by its path. |
| fedramp_list_documentsA | List documents in the corpus, optionally filtered to a section prefix. |
| fedramp_get_ruleA | Retrieve a rule (or NIST control) by its ID, with every place it appears. |
| fedramp_get_definitionA | Look up a FedRAMP defined term by name, alias, or FRD ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| source_info | Provenance of the bundled corpus: source repo, pinned commit, sync time. |
TDQS
Scored across 5 tools
Each tool targets a distinct operation: term definition lookup, full document retrieval, rule/control lookup, document listing, and full-text search. No overlap in functionality.
All tools use the 'fedramp_verb_noun' pattern in snake_case (e.g., fedramp_get_definition, fedramp_list_documents). No deviations or mixed conventions.
Five tools cover the essential operations for a rules corpus (search, retrieve documents/rules/definitions, list documents). Well-scoped and not excessive.
Covers CRUD-like operations for reading (get, list, search). Missing bulk listing of all rules or definitions, but list_documents and search can compensate. Minor gap.