eex_connector — Boncourant MCP Resource
eex_connector
is one of 1 resource on the
Boncourant
MCP server. Connect the server and your client can attach it as context.
by client
How to attach eex_connector from your client
- Claude Code Boncourant Resource/eex_connector run in your project directory
- Claude Desktop Boncourant Resource/eex_connector ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Boncourant Resource/eex_connector ~/.cursor/mcp.json
- VS Code Boncourant Resource/eex_connector .vscode/mcp.json
- Zed Boncourant Resource/eex_connector ~/.config/zed/settings.json
- Windsurf Boncourant Resource/eex_connector ~/.codeium/windsurf/mcp_config.json
- Cline Boncourant Resource/eex_connector ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Boncourant Resource/eex_connector ~/.gemini/settings.json
- Grok Boncourant Resource/eex_connector .mcp.json (in your project root)
- ChatGPT Boncourant Resource/eex_connector Settings → Connectors → Advanced → Developer mode
- Claude.ai Boncourant Resource/eex_connector Settings → Connectors → Add custom connector
- LangChain Boncourant Resource/eex_connector pip install langchain-mcp-adapters
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.