Cursor Systemia Field Library match_contractor_problem
How to: Cursor Systemia Field Library match_contractor_problem
Add Systemia Field Library to Cursor
-
01
Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"systemia-field-library": {
"url": "https://base44.app/api/apps/6a54381e147576b18ac94d8f/functions/fieldLibraryAgentMcp"
}
}
}-
02
Save the file and restart Cursor.
-
03
Ask for something match_contractor_problem does. Cursor lists the server's tools on connect and calls match_contractor_problem itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Systemia Field Library's identifier in your config matches the one above exactly.
Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs
Same tool, other clients
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.