match_contractor_problem — Systemia Field Library MCP Tool
match_contractor_problem
(match contractor problem) is one of 3 tools on the
Systemia Field Library
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call match_contractor_problem from your client
- Claude Code Systemia Field Library match_contractor_problem run in your project directory
- Claude Desktop Systemia Field Library match_contractor_problem ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Systemia Field Library match_contractor_problem ~/.cursor/mcp.json
- VS Code Systemia Field Library match_contractor_problem .vscode/mcp.json
- Zed Systemia Field Library match_contractor_problem ~/.config/zed/settings.json
- Windsurf Systemia Field Library match_contractor_problem ~/.codeium/windsurf/mcp_config.json
- Cline Systemia Field Library match_contractor_problem ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Systemia Field Library match_contractor_problem ~/.gemini/settings.json
- Grok Systemia Field Library match_contractor_problem .mcp.json (in your project root)
- ChatGPT Systemia Field Library match_contractor_problem Settings → Connectors → Advanced → Developer mode
- Claude.ai Systemia Field Library match_contractor_problem Settings → Connectors → Add custom connector
- LangChain Systemia Field Library match_contractor_problem pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http systemia-field-library https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 September 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.