match_problem — Claim Done MCP Tool
match_problem
(match problem) is one of 7 tools on the
Claim Done
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call match_problem from your client
- Claude Code Claim Done match_problem run in your project directory
- Claude Desktop Claim Done match_problem ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Claim Done match_problem ~/.cursor/mcp.json
- VS Code Claim Done match_problem .vscode/mcp.json
- Zed Claim Done match_problem ~/.config/zed/settings.json
- Windsurf Claim Done match_problem ~/.codeium/windsurf/mcp_config.json
- Cline Claim Done match_problem ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Claim Done match_problem ~/.gemini/settings.json
- Grok Claim Done match_problem .mcp.json (in your project root)
- ChatGPT Claim Done match_problem Settings → Connectors → Advanced → Developer mode
- Claude.ai Claim Done match_problem Settings → Connectors → Add custom connector
- LangChain Claim Done match_problem pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http claimdone https://claimdone.com.au/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 13 October 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.