TamingDNS finding-code registry — TamingDNS MCP Resource
TamingDNS finding-code registry
is one of 1 resource on the
TamingDNS
MCP server. Connect the server and your client can attach it as context.
by client
How to attach TamingDNS finding-code registry from your client
- Claude Code TamingDNS Resource/TamingDNS finding-code registry run in your project directory
- Claude Desktop TamingDNS Resource/TamingDNS finding-code registry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TamingDNS Resource/TamingDNS finding-code registry ~/.cursor/mcp.json
- VS Code TamingDNS Resource/TamingDNS finding-code registry .vscode/mcp.json
- Zed TamingDNS Resource/TamingDNS finding-code registry ~/.config/zed/settings.json
- Windsurf TamingDNS Resource/TamingDNS finding-code registry ~/.codeium/windsurf/mcp_config.json
- Cline TamingDNS Resource/TamingDNS finding-code registry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TamingDNS Resource/TamingDNS finding-code registry ~/.gemini/settings.json
- Grok TamingDNS Resource/TamingDNS finding-code registry .mcp.json (in your project root)
- ChatGPT TamingDNS Resource/TamingDNS finding-code registry Settings → Connectors → Advanced → Developer mode
- Claude.ai TamingDNS Resource/TamingDNS finding-code registry Settings → Connectors → Add custom connector
- LangChain TamingDNS Resource/TamingDNS finding-code registry pip install langchain-mcp-adapters
TamingDNS also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 6 November 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.