This repository was archived by the owner on Apr 15, 2026. It is now read-only.
Repository navigation
Troubleshooting
Ethan Troy edited this page Jan 14, 2026
·
1 revision
Common issues and solutions for fedramp-docs-mcp.
mkdir -p ~/.npm-global
npm config set prefix '~/.npm-global'
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc
npm install -g fedramp-docs-mcpEnsure Node.js is properly installed:
node --version # Should be 18+
npm --version # Should be 9+Expected. The server clones FedRAMP/docs (~50MB) on first run. Subsequent runs use the cache.
Repository clone may have failed. Delete cache and retry:
rm -rf ~/.cache/fedramp-docs
npx fedramp-docs-mcpCheck network connectivity:
curl -I https://github.comBehind a proxy? Configure git:
git config --global http.proxy http://proxy:8080Increase Node.js memory:
NODE_OPTIONS="--max-old-space-size=4096" npx fedramp-docs-mcp-
Check config file location:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Validate JSON syntax:
cat ~/Library/Application\ Support/Claude/claude_desktop_config.json | jq .
-
Restart Claude Desktop completely
Test the server directly:
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | npx fedramp-docs-mcpMCP uses stdio. Run with -it:
docker run -it fedramp-docs-mcpdocker run -it --user $(id -u):$(id -g) fedramp-docs-mcpEnable verbose logging:
DEBUG=* npx fedramp-docs-mcp- Check GitHub Issues
- Open a new issue with:
- Node.js version
- Operating system
- Error message
- Steps to reproduce
Getting Started
Reference
Guides
Links