Example Federal Register document — federal regulations mcp server MCP Resource

Example Federal Register document 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 Federal Register document from your client

• Claude Code federal regulations mcp server Resource/Example Federal Register document run in your project directory
• Claude Desktop federal regulations mcp server Resource/Example Federal Register document ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor federal regulations mcp server Resource/Example Federal Register document ~/.cursor/mcp.json
• VS Code federal regulations mcp server Resource/Example Federal Register document .vscode/mcp.json
• Zed federal regulations mcp server Resource/Example Federal Register document ~/.config/zed/settings.json
• Windsurf federal regulations mcp server Resource/Example Federal Register document ~/.codeium/windsurf/mcp_config.json
• Cline federal regulations mcp server Resource/Example Federal Register document ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI federal regulations mcp server Resource/Example Federal Register document ~/.gemini/settings.json
• Grok federal regulations mcp server Resource/Example Federal Register document .mcp.json (in your project root)
• ChatGPT federal regulations mcp server Resource/Example Federal Register document Settings → Connectors → Advanced → Developer mode
• Claude.ai federal regulations mcp server Resource/Example Federal Register document Settings → Connectors → Add custom connector
• LangChain federal regulations mcp server Resource/Example Federal Register document pip install langchain-mcp-adapters

Other resources on this server

• Example CFR section (40 CFR 50.1)

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.