rules_no — registry-mcp — national company registries MCP Resource

rules_no is one of 3 resources on the registry-mcp — national company registries MCP server. Connect the server and your client can attach it as context.

by client

How to attach rules_no from your client

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

Other resources on this server

• rules_gb
• rules_se

registry-mcp — national company registries also offers 3 prompts — things you invoke, where a resource is context you attach.

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.