MCP Allowlist Request - Base44

Hi Square team,

Here from Base44, an AI app and agent builder. We’d love to let our users connect their Square accounts to our agents through your hosted MCP server (mcp.squareup.com), and we understand MCP clients need to be on your allowlist first. Would it be possible to add us?

Here are our details:

Client name: Base44 MCP Client
Company: Base44 (base44.com)
Domains: app.base44.com, connectors.base44.com
Redirect URIs: https://app.base44.com/api/user/mcp-connections/oauth/callback and https://connectors.base44.com/api/oauth/callback
Auth: OAuth authorization code with PKCE (S256) and dynamic client registration

Sellers would sign in and grant access through Square, then work with their orders, catalog and customers from chat. We already offer a Square connector for our users’ apps, so this would round that out nicely.

Happy to share anything else you need. Thanks so much!

Welcome to the Developer Forum!

I’ve made the request to allowlist your URIs and it usually takes a few days to get completed. Please check back again next week and let us know here if you still don’t have access by the end of next week.

Hi, thanks a lot! Registration and the OAuth consent screen work for us now. Really appreciate your help.

Hi Square team,

I’m Corey Saxe with Montgomery Equipment, a Square seller using the Square connector through Cursor/Grok Bot. We’d like to restore authorization to your hosted MCP server. Our attempts on November 6–7, 2026 failed with:

Invalid redirect URI: https://www.cursor.com/agents/mcp/oauth/callback - domain not in allowlist

Here are the details:

  • Client name: “Cursor,” as identified in Cursor’s original allowlist request.
  • Affected company: Montgomery Equipment. We’re a seller using the connector, not the provider of the OAuth client.
  • Callback domain: www.cursor.com.
  • Rejected redirect URI: https://www.cursor.com/agents/mcp/oauth/callback.
  • Authentication: Cursor’s original request describes OAuth with dynamic client registration, a public client using token_endpoint_auth_method: none, and PKCE S256. I cannot independently confirm the registration payload used in our failed attempts.

Square’s October 29 reply on Cursor’s existing allowlist request says, “These should be enabled,” but the callback above is still rejected for us.

Could you confirm whether this exact redirect URI is allowed, what correction is needed, and which team can coordinate with Cursor/Grok Bot if necessary? Please let us know the next step and when we should try authorization again.

Thank you,
Corey Saxe
Montgomery Equipment