resource_access — BrunoSan Intelligence Concierge MCP Resource

resource_access is one of 3 resources on the BrunoSan Intelligence Concierge MCP server. Connect the server and your client can attach it as context.

by client

How to attach resource_access from your client

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

Other resources on this server

• resource_catalog
• resource_llms

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.