get_config_resource — nukez mcp MCP Resource

get_config_resource is one of 4 resources on the nukez mcp MCP server. Connect the server and your client can attach it as context.

by client

How to attach get_config_resource from your client

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

Other resources on this server

• get_wallet_resource
• get_instructions_resource
• get_sandbox_upload_playbook

nukez mcp also offers 2 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.