{
  "markdown": "# Trestle MCP\n\nMCP server to easily use [compliance-trestle](https://github.com/oscal-compass/compliance-trestle) (OSCAL tool) from Claude, Roo, or any MCP-compliant client.\n\nmcp-name: io.github.oscal-compass/compliance-trestle-mcp\n\n## Getting Started\n\nThis project can be used in the following two ways:\n\n- **[Usage from Coding Agent (Roo Code)](#usage-from-roocode)**: Use Trestle-MCP from Roo Code via MCP.\n- **[Usage from CLI (MCP Client)](#usage-from-cli-mcp-client)**: Invoke Trestle-MCP directly using an MCP CLI client.\n\nChoose the option that best fits your workflow.\n\n## Usage from RooCode\n\n1. Add the following JSON to `.roo/mcp.json` (Roo workspace):\n    \n    ```json\n    {\n        \"mcpServers\": {\n            \"trestle\": {\n                \"command\": \"uvx\",\n                \"args\": [\"--from\", \"compliance-trestle-mcp\", \"trestle-mcp\"]\n            }\n        }\n    }\n    ```\n\n2. Open Roo, confirm `trestle` tools are listed in the MCP panel, and execute as needed.\n\n    https://github.com/user-attachments/assets/59215549-cad9-4101-baa4-ecba77ac3904\n\n---\n\n## Usage from CLI (MCP Client)\n\n#### Step 1: Write your `mcp.json` config\n\n```json\n{\n    \"mcpServers\": {\n        \"trestle\": {\n            \"command\": \"uvx\",\n            \"args\": [\"--from\", \"./trestle-mcp-tmp\", \"trestle-mcp\"]\n        }\n    }\n}\n```\n\nSave this as `mcp.json` in your current directory.\n\n#### Step 2: List Available Tools\n\n```\nuvx mcp-cli tools --config-file mcp.json\n```\n\nSample output (tools available):\n\n```\n6 Available Tools\n┌─────────┬─────────────────────────────────┬───────────────────────────────────────────────────────────────────┐\n│ Server  │ Tool                            │ Description                                                       │\n├─────────┼─────────────────────────────────┼───────────────────────────────────────────────────────────────────┤\n│ trestle │ trestle_init                    │ Initialize a trestle working directory.                           │\n│ trestle │ trestle_import                  │ Import an existing OSCAL model into the trestle workspace.        │\n│ trestle │ trestle_author_catalog_generate │ Generate Catalog controls in markdown form from a catalog         │\n│ trestle │ trestle_author_profile_generate │ Generate markdown documentation set for controls defined in profile│\n│ trestle │ trestle_author_profile_resolve  │ Resolve an OSCAL profile to a resolved profile catalog.           │\n│ trestle │ trestle_author_profile_assemble │ Assemble markdown controls into a Profile JSON file.              │\n└─────────┴─────────────────────────────────┴───────────────────────────────────────────────────────────────────┘\n```\n\n#### Step 3: Execute a Tool (e.g., `trestle_init`)\n\nStart MCP interactive shell:\n\n```\nuvx mcp-cli interactive --config-file mcp.json\n```\n\nThen run, for example:\n\n```\n> execute trestle_init '{\"params\": {}}'\n```\n\nTypical result:\n\n```\n✓ ✅ Tool executed successfully\n{\n  \"result\": {\n    ...\n    \"content\": [\n      {\n        \"type\": \"text\",\n        \"text\": \"✅ Trestle workspace initialized successfully\"\n      }\n    ]\n  }\n}\n```\n\nYou'll see folders as follows: \n```\nassessment-plans    catalogs               plan-of-action-and-milestones  system-security-plans\nassessment-results  component-definitions  profiles\n```\n\n---\n\n## Tool List & Quick Reference\n\n- `trestle_init`: Initialize a trestle workspace\n- `trestle_import`: Import OSCAL models (Catalog/Profile/etc.) from a file or URL\n- `trestle_author_catalog_generate`: Generate markdown controls from a catalog\n- `trestle_author_profile_generate`: Generate markdown for profiles\n- `trestle_author_profile_resolve`: Resolve profile to catalog\n- `trestle_author_profile_assemble`: Assemble markdown controls into profile JSON\n- `trestle_task_csv_to_oscal_cd`: Convert a CSV mapping file into an OSCAL component definition\n- `trestle_task_xlsx_to_oscal_poam`: Convert a FedRAMP-format XLSX spreadsheet into an OSCAL Plan of Action and Milestones (POA&M)\n- `trestle_validate`: Validate a standalone OSCAL file (any top-level model, e.g. POA&M) against the OSCAL schema (and trestle's semantic checks)\n\nFor advanced use, refer to official [compliance-trestle docs](https://oscal-compass.dev/compliance-trestle/latest/) or [developer documents](docs/command-specs-development.md) in this repo.\n\n## Troubleshooting & Help\n\n- Make sure [uvx](https://docs.astral.sh/uv/getting-started/installation/) is installed and on your PATH.\n- If you see command/module errors, check the MCP server path in `mcp.json` is correct.\n\n______________________________________________________________________\n\nWe are a Cloud Native Computing Foundation sandbox project.\n\n<picture>\n  <source media=\"(prefers-color-scheme: dark)\" srcset=\"https://www.cncf.io/wp-content/uploads/2022/07/cncf-white-logo.svg\">\n  <img src=\"https://www.cncf.io/wp-content/uploads/2022/07/cncf-color-bg.svg\" width=300 />\n</picture>\n\nThe Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see [Trademark Usage](https://www.linuxfoundation.org/legal/trademark-usage).\n\n*OSCAL Compass is an independent open source project. It is not affiliated with, endorsed by, or sponsored by the National Institute of Standards and Technology (NIST) or any other government agency.*\n\n*OSCAL Compass was originally contributed by IBM.*\n",
  "bytes": 5316,
  "sha": "121212afef26f113d82253889336b59ba5fcc50687da4142a0f2ccfbb420efde",
  "repo_slug": "oscal-compass/compliance-trestle-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_oscal_compass_compliance_trest_27710324/readme"
}