# Request for MCP Connector \> Add DISPUTES\_READ **URL:** \ **Category:** MCP\ **Tags:** disputes-api\ **Created:** [May 5, 2026, 2:13pm UTC](https://developer.squareup.com/forums/t/request-for-mcp-connector-add-disputes-read/26004 "2026-05-05T14:13:28Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ashlinconroy](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@ashlinconroy](https://developer.squareup.com/forums/u/ashlinconroy)\ **Post date:** [May 5, 2026, 2:13pm UTC](https://developer.squareup.com/forums/t/request-for-mcp-connector-add-disputes-read/26004/1 "2026-05-05T14:13:28Z")
**Request: Add DISPUTES\_READ scope to the Square MCP connector** The Square connector currently doesn’t include the DISPUTES\_READ OAuth scope. This means we can’t access dispute/chargeback data through the connector, which is needed for full payout reconciliation. We’re building an automated reconciliation system that matches Square batch payouts to revenue categories and generates journal entries. Charges, refunds, fees, and payment data all work great through the connector. The only gap is disputes — we need to see which payments were charged back, the dispute amounts, and which payouts the deductions hit. The fix should be straightforward: add DISPUTES\_READ to the list of scopes the connector requests during OAuth authorization. Current scopes appear to include: PAYMENTS\_READ, ORDERS\_READ, MERCHANT\_PROFILE\_READ, BANK\_ACCOUNTS\_READ, PAYOUTS\_READ Requested addition: DISPUTES\_READ ---
**Author:** ![rsata](https://avatars.discourse-cdn.com/v4/letter/r/57b2e6/32.png) [@rsata](https://developer.squareup.com/forums/u/rsata)\ **Post date:** [May 5, 2026, 8:30pm UTC](https://developer.squareup.com/forums/t/request-for-mcp-connector-add-disputes-read/26004/2 "2026-05-05T20:30:58Z")
@ashlinconroy thanks for reaching out. When you authenticate the MCP server you should have an option to include DISPUTES\_READ in your scopes. Could you try re-authenticating with that scope and let us know if that solves it?