match_need — concierge MCP Tool
match_need
(match need) is one of 18 tools on the
concierge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call match_need from your client
- Claude Code concierge match_need run in your project directory
- Claude Desktop concierge match_need ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor concierge match_need ~/.cursor/mcp.json
- VS Code concierge match_need .vscode/mcp.json
- Zed concierge match_need ~/.config/zed/settings.json
- Windsurf concierge match_need ~/.codeium/windsurf/mcp_config.json
- Cline concierge match_need ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI concierge match_need ~/.gemini/settings.json
- Grok concierge match_need .mcp.json (in your project root)
- ChatGPT concierge match_need Settings → Connectors → Advanced → Developer mode
- Claude.ai concierge match_need Settings → Connectors → Add custom connector
- LangChain concierge match_need pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http concierge https://concierge.eacpartners.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.