compute_trade_spend — aurgus MCP Tool
compute_trade_spend
(compute trade spend) 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 compute_trade_spend from your client
- Claude Code aurgus compute_trade_spend run in your project directory
- Claude Desktop aurgus compute_trade_spend ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor aurgus compute_trade_spend ~/.cursor/mcp.json
- VS Code aurgus compute_trade_spend .vscode/mcp.json
- Zed aurgus compute_trade_spend ~/.config/zed/settings.json
- Windsurf aurgus compute_trade_spend ~/.codeium/windsurf/mcp_config.json
- Cline aurgus compute_trade_spend ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI aurgus compute_trade_spend ~/.gemini/settings.json
- Grok aurgus compute_trade_spend .mcp.json (in your project root)
- ChatGPT aurgus compute_trade_spend Settings → Connectors → Advanced → Developer mode
- Claude.ai aurgus compute_trade_spend Settings → Connectors → Add custom connector
- LangChain aurgus compute_trade_spend 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
- sign_close
- export_workpapers
- ingest_agreement
- compose_agreement
- ingest
- compute_close
- confirm_grouping
- report
- set_cadence
- close_agreement
- defunct_agreement
- true_up
- edit_agreement_rates
- 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.