Example CFR section (40 CFR 50.1) — federal regulations mcp server MCP Resource
Example CFR section (40 CFR 50.1)
is one of 2 resources on the
federal regulations mcp server
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Example CFR section (40 CFR 50.1) from your client
- Claude Code federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) run in your project directory
- Claude Desktop federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) ~/.cursor/mcp.json
- VS Code federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) .vscode/mcp.json
- Zed federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) ~/.config/zed/settings.json
- Windsurf federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) ~/.codeium/windsurf/mcp_config.json
- Cline federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) ~/.gemini/settings.json
- Grok federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) .mcp.json (in your project root)
- ChatGPT federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) Settings → Connectors → Advanced → Developer mode
- Claude.ai federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) Settings → Connectors → Add custom connector
- LangChain federal regulations mcp server Resource/Example CFR section (40 CFR 50.1) pip install langchain-mcp-adapters
Other resources on this server
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.