MCP Client Setup

MCP Client Setup

Configure various MCP clients to use fedramp-docs-mcp.

Claude Desktop

macOS

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "fedramp-docs": {
      "command": "npx",
      "args": ["-y", "fedramp-docs-mcp"]
    }
  }
}

Windows

Edit %APPDATA%\Claude\claude_desktop_config.json with the same configuration.

Restart Claude Desktop after saving.

Cursor

Add to Cursor MCP settings:

{
  "mcpServers": {
    "fedramp-docs": {
      "command": "npx",
      "args": ["-y", "fedramp-docs-mcp"]
    }
  }
}

VS Code with Continue

Edit ~/.continue/config.json:

{
  "mcpServers": [
    {
      "name": "fedramp-docs",
      "command": "npx",
      "args": ["-y", "fedramp-docs-mcp"]
    }
  ]
}

LM Studio

Edit ~/.lmstudio/mcp.json:

{
  "mcpServers": {
    "fedramp-docs": {
      "command": "fedramp-docs-mcp",
      "args": []
    }
  }
}

Kiro

Kiro is AWS's spec-driven IDE with native MCP support.

Edit ~/.kiro/settings/mcp.json (global) or .kiro/settings/mcp.json (project):

{
  "mcpServers": {
    "fedramp-docs": {
      "command": "npx",
      "args": ["-y", "fedramp-docs-mcp"],
      "env": {
        "FEDRAMP_DOCS_AUTO_UPDATE": "true"
      }
    }
  }
}

Save the file - Kiro automatically loads MCP servers on config change.

Docker-Based Setup

For any client:

{
  "mcpServers": {
    "fedramp-docs": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "fedramp-cache:/root/.cache/fedramp-docs",
        "ghcr.io/ethanolivertroy/fedramp-docs-mcp:latest"
      ]
    }
  }
}

With Environment Variables

{
  "mcpServers": {
    "fedramp-docs": {
      "command": "npx",
      "args": ["-y", "fedramp-docs-mcp"],
      "env": {
        "FEDRAMP_DOCS_AUTO_UPDATE": "true",
        "FEDRAMP_DOCS_UPDATE_CHECK_HOURS": "12"
      }
    }
  }
}

Verification

After setup, ask your AI:

"Call the health_check tool from fedramp-docs"

You should see indexed file counts and repository info.

Troubleshooting

• Server not appearing: Check JSON syntax, restart client
• Command not found: Ensure Node.js/npm in PATH
• First run slow: Initial clone takes 1-2 minutes

See Troubleshooting for more solutions.