fieldedge_get_agreement — FieldEdge MCP by usefulapi MCP Tool
fieldedge_get_agreement
(fieldedge get agreement) is one of 45 tools on the
FieldEdge MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call fieldedge_get_agreement from your client
- Claude Code FieldEdge MCP by usefulapi fieldedge_get_agreement run in your project directory
- Claude Desktop FieldEdge MCP by usefulapi fieldedge_get_agreement ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FieldEdge MCP by usefulapi fieldedge_get_agreement ~/.cursor/mcp.json
- VS Code FieldEdge MCP by usefulapi fieldedge_get_agreement .vscode/mcp.json
- Zed FieldEdge MCP by usefulapi fieldedge_get_agreement ~/.config/zed/settings.json
- Windsurf FieldEdge MCP by usefulapi fieldedge_get_agreement ~/.codeium/windsurf/mcp_config.json
- Cline FieldEdge MCP by usefulapi fieldedge_get_agreement ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FieldEdge MCP by usefulapi fieldedge_get_agreement ~/.gemini/settings.json
- Grok FieldEdge MCP by usefulapi fieldedge_get_agreement .mcp.json (in your project root)
- ChatGPT FieldEdge MCP by usefulapi fieldedge_get_agreement Settings → Connectors → Advanced → Developer mode
- Claude.ai FieldEdge MCP by usefulapi fieldedge_get_agreement Settings → Connectors → Add custom connector
- LangChain FieldEdge MCP by usefulapi fieldedge_get_agreement pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fieldedge https://fieldedge.usefulapi.io/mcpOther tools on this server
- fieldedge_list_work_orders
- fieldedge_get_work_order
- fieldedge_search_work_orders_by_address
- fieldedge_list_work_order_assignments
- fieldedge_search_customers
- fieldedge_get_customer
- fieldedge_get_customer_by_phone
- fieldedge_search_customers_by_address
- fieldedge_list_customer_notes
- fieldedge_list_customer_attachments
- fieldedge_list_tags
- fieldedge_list_invoices
- fieldedge_get_invoice
- fieldedge_list_quotes
- fieldedge_get_quote
- fieldedge_list_agreements
- fieldedge_list_employees
- fieldedge_get_employee
- fieldedge_list_business_units
- fieldedge_get_business_unit
- fieldedge_list_lead_sources
- fieldedge_get_lead_source
- fieldedge_list_tasks
- fieldedge_get_task_bundle
- fieldedge_list_items
- fieldedge_get_item
- fieldedge_list_item_categories
- fieldedge_get_item_category
- fieldedge_list_sales_tax_codes
- fieldedge_list_warehouses
- fieldedge_get_warehouse
- fieldedge_get_lead
- fieldedge_get_company
- fieldedge_create_customer
- fieldedge_create_customer_note
- fieldedge_update_customer_note
- fieldedge_create_tag
- fieldedge_add_customer_tag
- fieldedge_remove_customer_tag
- fieldedge_create_work_order
- fieldedge_update_work_order
- fieldedge_assign_technician
- fieldedge_update_assignment_status
- fieldedge_remove_assignment
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.