Square MCP Extension

🎥 Square MCP Server Video Walkthrough

This tutorial will get you started with the Square MCP server to enable interactive and automated work for your Square seller account. The Square MCP server is an open source project that allows you to interact with the Square API using Goose.

Square offers two versions of the MCP server:

1. Remote MCP server hosted by Square, which uses OAuth for authentication and allows fine-grained permissions on API usage.
2. Local MCP server that you can run on your own machine, which uses an access token for authentication and allows full API access.

info

Note that you'll need Node.js installed on your system to run installation commands, which use npx.

Square Remote MCP

TLDR

Goose Desktop

Launch the installer

Goose CLI

Command

npx mcp-remote https://mcp.squareup.com/sse

Configuration

Goose Desktop

1. Launch the installer
2. Goose will open and ask you to confirm installation.
3. Goose should open a browser tab to an OAuth permissions page. Double-check which permissions you want to allow, and click 'Grant Access'.
4. It will ask you to login or reauthenticate to Square, and may ask you to confirm the permissions you want to allow.

Goose CLI

1. Run the configure command:

goose configure

1. Choose to add a Command-line Extension

  ┌   goose-configure 
  │
  ◇  What would you like to configure?
  │  Add Extension (Connect to a new extension) 
  │
  ◆  What type of extension would you like to add?
  │  ○ Built-in Extension 
  │  ○ Command-line Extension (Run a local command or script)
  │  ● Remote Extension 
  └ 

1. Give your extension a name

  ┌   goose-configure 
  │
  ◇  What would you like to configure?
  │  Add Extension (Connect to a new extension) 
  │
  ◇  What type of extension would you like to add?
  │  Remote Extension 
  │
  ◆  What would you like to call this extension?
  │  square-mcp-remote
  └ 

1. Enter the SSE URI

  ┌   goose-configure 
  │
  ◇  What would you like to configure?
  │  Add Extension (Connect to a new extension) 
  │
  ◇  What type of extension would you like to add?
  │  Remote Extension
  │
  ◇  What would you like to call this extension?
  │  square-mcp-remote
  │
  ◆  What is the SSE endpoint URI?
  │  https://mcp.squareup.com/sse
  └ 

1. Enter the number of seconds Goose should wait for actions to complete before timing out. Default is 300s

 ┌   goose-configure 
 │
 ◇  What would you like to configure?
 │  Add Extension (Connect to a new extension) 
 │
 ◇  What type of extension would you like to add?
 │  Remote Extension
 │
 ◇  What would you like to call this extension?
 │  square-mcp-remote
 │
 ◆  What is the SSE endpoint URI?
 │  https://mcp.squareup.com/sse
 │
 ◆  Please set the timeout for this tool (in secs):
 │  300
 └ 

1. Choose to add a description. If you select "Yes" here, you will be prompted to enter a description for the extension.

 ┌   goose-configure 
 │
 ◇  What would you like to configure?
 │  Add Extension (Connect to a new extension) 
 │
 ◇  What type of extension would you like to add?
 │  Remote Extension
 │
 ◇  What would you like to call this extension?
 │  square-mcp-remote
 │
 ◆  What is the SSE endpoint URI?
 │  https://mcp.squareup.com/sse
 │
 ◆  Please set the timeout for this tool (in secs):
 │  300
 │
 ◇  Would you like to add a description?
 │  No
 └ 

1. Obtain a Square Access Token and paste it in.

 ┌   goose-configure 
 │
 ◇  What would you like to configure?
 │  Add Extension (Connect to a new extension) 
 │
 ◇  What type of extension would you like to add?
 │  Remote Extension
 │
 ◇  What would you like to call this extension?
 │  square-mcp-remote
 │
 ◆  What is the SSE endpoint URI?
 │  https://mcp.squareup.com/sse
 │
 ◇  Please set the timeout for this tool (in secs):
 │  300
 │
 ◇  Would you like to add a description?
 │  No
 │
 ◆  Would you like to add environment variables?
 │  No
 │
 └  Added square-mcp-remote extension

Square Local MCP

TLDR

Goose Desktop

Launch the installer

Goose CLI

Command

npx square-mcp-server start

Environment Variables

ACCESS_TOKEN: <YOUR_API_KEY>
SANDBOX: <true/false>
PRODUCTION: <true/false>

Note that you'll use SANDBOX -or- PRODUCTION, not both, and your ACCESS_TOKEN will either be a sandbox or production token, depending on which environment you choose.

Configuration

Goose Desktop

1. Launch the installer
2. Press Yes to confirm the installation
3. Get your Square Access Token and paste it in
4. Keep SANDBOX as the environment variable, or change to PRODUCTION, and set its value to true
5. Click Save Configuration
6. Scroll to the top and click Exit from the upper left corner

Goose CLI

1. Run the configure command:

goose configure

1. Choose to add a Command-line Extension

  ┌   goose-configure 
  │
  ◇  What would you like to configure?
  │  Add Extension (Connect to a new extension) 
  │
  ◆  What type of extension would you like to add?
  │  ○ Built-in Extension 
  │  ● Command-line Extension (Run a local command or script)
  │  ○ Remote Extension 
  └ 

1. Give your extension a name

  ┌   goose-configure 
  │
  ◇  What would you like to configure?
  │  Add Extension (Connect to a new extension) 
  │
  ◇  What type of extension would you like to add?
  │  Command-line Extension 
  │
  ◆  What would you like to call this extension?
  │  square-mcp
  └ 

1. Enter the command

  ┌   goose-configure 
  │
  ◇  What would you like to configure?
  │  Add Extension (Connect to a new extension) 
  │
  ◇  What type of extension would you like to add?
  │  Command-line Extension 
  │
  ◇  What would you like to call this extension?
  │  square-mcp
  │
  ◆  What command should be run?
  │  npx square-mcp-server start
  └ 

1. Enter the number of seconds Goose should wait for actions to complete before timing out. Default is 300s

 ┌   goose-configure 
 │
 ◇  What would you like to configure?
 │  Add Extension (Connect to a new extension) 
 │
 ◇  What type of extension would you like to add?
 │  Command-line Extension 
 │
 ◇  What would you like to call this extension?
 │  square-mcp
 │
 ◇  What command should be run?
 │  npx square-mcp-server start
 │
 ◆  Please set the timeout for this tool (in secs):
 │  300
 │
 └ 

1. Choose to add a description. If you select "Yes" here, you will be prompted to enter a description for the extension.

 ┌   goose-configure 
 │
 ◇  What would you like to configure?
 │  Add Extension (Connect to a new extension) 
 │
 ◇  What type of extension would you like to add?
 │  Command-line Extension 
 │
 ◇  What would you like to call this extension?
 │  square-mcp
 │
 ◇  What command should be run?
 │  npx square-mcp-server start
 │
 ◆  Please set the timeout for this tool (in secs):
 │  300
 │
 ◇  Would you like to add a description?
 │  No
 │
 └ 

1. Obtain a Square Access Token and paste it in.

 ┌   goose-configure 
 │
 ◇  What would you like to configure?
 │  Add Extension (Connect to a new extension) 
 │
 ◇  What type of extension would you like to add?
 │  Command-line Extension 
 │
 ◇  What would you like to call this extension?
 │  square-mcp
 │
 ◇  What command should be run?
 │  npx square-mcp-server start
 │
 ◇  Please set the timeout for this tool (in secs):
 │  300
 │
 ◇  Would you like to add a description?
 │  No
 │
 ◆  Would you like to add environment variables?
 │  Yes 
 │
 ◇  Environment variable name:
 │  ACCESS_TOKEN
 │
 ◇  Environment variable value:
 │  ▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪
 │
 ◇  Add another environment variable?
 │  Yes
 │
 ◇  Environment variable name:
 │  SANDBOX
 │
 ◇  Environment variable value:
 │  true
 └  Added square-mcp extension

info

Change the SANDBOX key to PRODUCTION if using a production token

Example Usage

The Square MCP server allows you to interact with Square's connect API with an extensive service catalog to access the Square API ecosystem.

Goose Prompt

( O)> Find my food menu from the following image and import these into my Square seller account. "my-burger-menu.png"

Here's the menu image used in the demo.

Goose Output

I'll help you import these menu items into your Square catalog. I'll use the Square API to create catalog items for each burger. Let me break this down into steps:

1. First, I'll check the catalog API service info and types
2. Then I'll create catalog items for each burger

Now let me check the type info for creating catalog objects

Now I'll start creating catalog items for each burger in your menu. I'll create them one by one using the catalog API. Let me process each burger:

(output truncated)

I've successfully created all the burger items from your menu in your Square catalog. Each burger has been added with:

- The exact name from your menu
- The full description
- The correct price
- A standard variation for ordering

Here's a summary of what was created:
- The Classic - $10.00
- Cheeseburger - $11.00
- Primetime Burger - $12.00
- Double Bacon - $14.00
- Texas Meatlover - $12.50
- Buffalo Burger - $12.00
- The Atomic - $12.50
- Little Bird - $11.00
- Mushroom Burger - $10.00

All items are now available in your Square catalog and ready for use in your point of sale system. Each burger includes its complete description and comes with a "Regular" variation at the specified price. The items are set as both sellable and stockable by default, and they're available at all locations.