xero: optional XERO_SCOPES setup field for post-April-2026 Custom Connections (1.0.1) - #453
Open
ericgyl817 wants to merge 1 commit into
Open
ericgyl817 wants to merge 1 commit into
ericgyl817 wants to merge 1 commit into
Conversation
…ated after 2026-04-29 (1.0.1)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Customer impact: CM-37: Xero users whose Custom Connection was created on or after 29 Apr 2026 always failed to connect with invalid_client, because the server asks Xero for old bundled scopes those connections reject; they can now enter their granted scopes in the new optional Xero scopes field and connect (on Grok Bot this also needs everysphere #1079195 so saved values reach the plugin).
XERO_SCOPES: "${XERO_SCOPES:-}", so Custom Connections created on or after 2026-04-29 can skip the bundled-scope token request that Xero rejects withinvalid_client(CM-37; upstream fix fix: try no-scope token request first for new custom connections XeroAPI/xero-mcp-server#288 is still unmerged, and the published 0.0.17 already honorsXERO_SCOPES)....with V1 scopes), a value takes theXERO_SCOPESpath; Cursor's expansion turns the blank default into"", which the server treats as unset.node scripts/validate-plugins.mjspasses.Note
Low Risk
Optional plugin configuration and env passthrough only; existing installs with a blank scopes field keep the same MCP env behavior.
Overview
Bumps the Xero plugin to 1.0.1 and adds an optional Xero scopes setup field (
XERO_SCOPES) wired throughmcp.jsonasXERO_SCOPES: "${XERO_SCOPES:-}"so the local@xeroapi/xero-mcp-servercan request granular OAuth scopes instead of the bundled set.README, CHANGELOG, and
plugin.jsonnow document that Custom Connections created on or after 2026-04-29 must supply space-separated scopes (e.g.accounting.invoices accounting.contacts); otherwise Xero returnsinvalid_client. Leaving the field blank preserves prior behavior for older connections.Reviewed by Cursor Bugbot for commit 503d627. Bugbot is set up for automated code reviews on this repo. Configure here.