edit_agreement_rates — aurgus MCP Tool Mutating
edit_agreement_rates
(edit agreement rates) is one of 37 tools on the
aurgus
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call edit_agreement_rates from your client
- Claude Code aurgus edit_agreement_rates run in your project directory
- Claude Desktop aurgus edit_agreement_rates ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor aurgus edit_agreement_rates ~/.cursor/mcp.json
- VS Code aurgus edit_agreement_rates .vscode/mcp.json
- Zed aurgus edit_agreement_rates ~/.config/zed/settings.json
- Windsurf aurgus edit_agreement_rates ~/.codeium/windsurf/mcp_config.json
- Cline aurgus edit_agreement_rates ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI aurgus edit_agreement_rates ~/.gemini/settings.json
- Grok aurgus edit_agreement_rates .mcp.json (in your project root)
- ChatGPT aurgus edit_agreement_rates Settings → Connectors → Advanced → Developer mode
- Claude.ai aurgus edit_agreement_rates Settings → Connectors → Add custom connector
- LangChain aurgus edit_agreement_rates pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aurgus https://mcp.aurgus.com/api/mcpOther tools on this server
- begin
- help
- release_notes
- explain
- request_real_run
- aurgus
- open_engagement
- engagement_status
- request_documents
- open_items
- receive_document
- compute_commission
- compute_revenue_contract
- compute_lease
- compute_trade_spend
- sign_close
- export_workpapers
- ingest_agreement
- compose_agreement
- ingest
- compute_close
- confirm_grouping
- report
- set_cadence
- close_agreement
- defunct_agreement
- true_up
- edit_agreement
- analyze
- save_report
- list_reports
- run_report
- recalculate
- settle
- trace
- export
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.