blueDEX transparency — blueDEX MCP Resource

blueDEX transparency is one of 2 resources on the blueDEX MCP server. Connect the server and your client can attach it as context.

by client

How to attach blueDEX transparency from your client

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

Other resources on this server

• Curated token lists

blueDEX 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 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.