Square is a financial technology company that provides payment processing hardware and software, business management tools, and banking services to help businesses of all sizes start, run, and grow their operations.
Why this server?
Provides access to Square's complete API ecosystem, enabling interactions with services such as catalog management, customer management, payment processing, order management, inventory tracking, appointment booking, gift cards, loyalty programs, and many other Square business services.
Why this server?
Provides access to Square API functionality through a Model Context Protocol (MCP) server
Why this server?
Provides comprehensive access to Square's API ecosystem, allowing for catalog management, order processing, payment handling, customer management, inventory tracking, subscription management, and other commerce operations through Square's platform.
Why this server?
The MCP server supports generating face images in square shape (one of the available shape options alongside circle and rounded rectangle).
Why this server?
Provides querying capabilities for Square payment processing data through SQL models.
Why this server?
Listed as a supported data source for accessing Square payment and point-of-sale data.
Why this server?
Provides SQL access to Square payments, orders, and customer data.
Why this server?
Allows SQL-based access to Square payment processing data.
Why this server?
Listed as a supported data source for integration, allowing access to Square data through the MCP server.
Why this server?
Allows querying Square payment and point-of-sale data through SQL.
Why this server?
Enables querying of Square payment processing and point-of-sale data through SQL interface
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Square data.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Provides read access to Square payment processing data through SQL interfaces, enabling natural language querying of transaction information.
Why this server?
Provides SQL-based access to Square data, enabling retrieval of payment processing information through natural language questions.
Why this server?
Listed as a supported data source that can be queried through the MCP server.
Why this server?
Listed as a supported data source for integration, enabling access to Square payment processing data through the CData JDBC Driver.
Why this server?
Allows access to Square payment and business data through SQL interfaces.
Why this server?
Allows SQL-based querying of Square payment processing data, including transactions, items, and customer information.
Why this server?
Listed as a supported data source for integration, allowing access to Square payment and business data.
Why this server?
Provides read-only access to Square data by exposing tables as relational SQL models, allowing retrieval of live data through simple MCP queries.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Enables querying Square data sources by exposing them as relational SQL models that can be accessed through natural language queries.
Why this server?
Enables SQL-based access to Square payment processing and business management data.
Why this server?
Enables SQL-based access to Square payment and point-of-sale data.
Why this server?
Allows read-only SQL querying of Square payment transactions, items, and customer data.
Why this server?
Allows SQL-based access to Square payment and point-of-sale data, including transactions, customers, and inventory.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver framework.
Why this server?
Provides read-only access to Square data through SQL models, allowing queries of Square data through natural language requests.
Why this server?
Allows access to Square payment platform data including transactions, customers, inventory, and sales analytics through SQL queries.
Why this server?
Provides read-only access to Square payment and business data through SQL queries, enabling retrieval of transactions and point-of-sale information
Why this server?
Provides read-only access to Square payment and POS data through SQL queries, enabling retrieval of transactions, inventory, and customer information
Why this server?
Enables querying of Square payment processing data including transactions, customer information, and point-of-sale analytics.
Why this server?
Allows querying Square payment processing data including transactions and customer information through SQL
Why this server?
Enables querying Square payment platform data including transactions, customers, and business analytics through SQL operations.
Why this server?
Enables SQL-based access to Square payment processing data, allowing querying of transactions, customers, and business metrics
Why this server?
Provides access to Square point-of-sale and payment processing data including transactions, inventory, customers, and business analytics through SQL queries.
Why this server?
Enables SQL querying of Square payment processing and point-of-sale data.
Why this server?
Allows access to Square payment processing and point-of-sale data including transactions and inventory
Why this server?
Provides access to Square payment data including transactions, customers, and business analytics through SQL operations
Why this server?
Provides access to Square payment and point-of-sale data including transactions and customer information through SQL queries
Why this server?
Provides access to Square point-of-sale and payment processing data
Why this server?
Provides access to Square payment processing and point-of-sale data
Why this server?
Allows access to Square payment processing data and point-of-sale information
Why this server?
Allows querying of Square point-of-sale and payment data through SQL interface
Why this server?
Allows SQL-based querying of Square payment processing and point-of-sale data
Why this server?
Provides SQL access to Square payment processing data through CData's JDBC driver
Why this server?
Enables retrieval of Square payment processing and point-of-sale data through SQL interface
Why this server?
Allows SQL-based access to Square payment and point-of-sale data, providing queries against transactions, payments, and merchant information.
Why this server?
Allows querying of Square payment processing data, transactions, and business analytics.
Why this server?
Provides access to Square payment and point-of-sale data including transactions, inventory, and customer information through SQL queries.
Why this server?
Allows SQL querying of Square point-of-sale and payment data including transactions, customers, and business analytics.
Why this server?
Enables access to Square point-of-sale data, transactions, and payment processing information
Why this server?
Allows querying of Square payment processing and point-of-sale system data
Why this server?
Provides tools for querying Square point-of-sale and payment data, enabling access to transactions and business metrics.
Why this server?
Enables access to Square payment platform data through SQL-like queries for transactions, inventory, and business information
Why this server?
Enables SQL access to Square payment and point-of-sale data
Why this server?
Allows querying of Square payment and point-of-sale data through relational SQL models.
Why this server?
Enables SQL queries against Square payment processing and point-of-sale data.
Why this server?
Allows querying of Square data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Enables access to Square payment processing data through relational SQL models, with tools for listing tables, retrieving column information, and executing SQL queries.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver, allowing for data retrieval from Square payment processing platform.
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver.
Why this server?
Provides SQL access to Square payment and point-of-sale data, including transactions, items, and customers.
Why this server?
Allows SQL-based access to Square payment and point-of-sale data.
Why this server?
Provides access to Square payment processing data through SQL-based tools for listing tables, retrieving column information, and executing SELECT queries.
Why this server?
Provides access to Square payment and point-of-sale data through SQL.
Why this server?
Provides access to SAS Data Sets containing Square data through SQL queries.
Why this server?
Provides SQL-based access to Square payment processing data through the MCP server.
Why this server?
Enables querying of Square payment and point-of-sale data through SQL interfaces.
Why this server?
Allows accessing Square payment processing data through SQL queries.
Why this server?
Provides access to Square payment processing data through SQL, enabling queries against transactions, customers, and inventory.
Why this server?
Enables SQL-based access to Square payment and point-of-sale data including transactions and items.
Why this server?
Allows querying Square payment and point-of-sale data via SQL models.
Why this server?
Provides read-only access to Square payment processing data.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for data access.
Why this server?
Integrates with Square's Goose AI assistant through configuration in Goose's config.yaml file
Why this server?
Listed as a supported data source that can be connected to through the CData JDBC driver, enabling data querying capabilities.
Why this server?
Listed as a supported data source that can be accessed through the CData JDBC driver integration.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for querying Square data.
Why this server?
Listed as a supported data source that can be integrated with the MCP server for retrieving data.
Why this server?
Allows querying Square payment and point-of-sale data.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Square data.
Why this server?
Offers read-only access to Square payment processing and point-of-sale data.
Why this server?
Provides access to Square payment and point-of-sale data including transactions, items, customers, and other business information through SQL queries.
Why this server?
Provides SQL-based access to Square payment processing data, supporting querying of transactions and merchant information.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Provides read-only access to Square payment and point-of-sale data, enabling queries for transactions, customers, and inventory.
Why this server?
Allows querying Square payment and business management data through SQL interfaces.
Why this server?
Allows querying Square payment processing data, providing access to transactions, payments, customers, and point-of-sale information.
Why this server?
Enables querying of Square point-of-sale and payment data through SQL interface
Why this server?
Provides SQL-based access to Square payment processing and point-of-sale data, including transactions, inventory, and business analytics.
Why this server?
Enables querying Square payment platform data including transactions, payments, and merchant information through SQL operations.
Why this server?
Allows querying Square payment processing data through SQL operations, providing access to transactions and business analytics.
Why this server?
Allows querying Square payment and point-of-sale transaction data.
Why this server?
Enables access to Square payment processing and point-of-sale data through SQL queries.
Why this server?
Enables read-only access to Square data through natural language queries.
Why this server?
Provides read access to Square payment processing data by exposing it as relational SQL models through the CData JDBC driver.
Why this server?
Allows access to payment and business data from Square accounts.
Why this server?
Provides read-only access to Square payment processing data, enabling queries on transactions, customers, and business analytics.
Why this server?
Provides SQL-based access to Square payment processing data, enabling queries for transactions, customers, and inventory information.
Why this server?
Allows SQL-based queries of Square payment processing data.
Why this server?
Included in the list of supported sources for data retrieval through the MCP server.
Why this server?
Provides SQL access to Square payment processing data, enabling queries on transactions, payments, and business analytics.
Why this server?
Allows accessing Square payment processing data including transactions and merchant information.
Why this server?
Enables querying of Square payment and point-of-sale data, providing access to transaction, inventory, and customer information through natural language questions.
Why this server?
Provides access to Square payment data including transactions, customers, and point-of-sale analytics.
Why this server?
Enables SQL querying of Square payment processing and point-of-sale transaction data
Why this server?
Provides access to Square payment processing data including transactions, customers, and business metrics.
Why this server?
Provides access to Square payment processing and point-of-sale data through SQL queries.
Why this server?
Provides read-only access to Square payment and business data through SQL queries, enabling retrieval of transaction and merchant information.
Why this server?
Allows querying of Square payments, orders, and inventory through SQL models.
Why this server?
Enables querying of Square payment processing data including transactions, customers, and business analytics.
Why this server?
Enables querying of Square payment processing data including transactions, customers, and business analytics
Why this server?
Enables SQL-based access to Square payment processing data.
Why this server?
Provides integration with Square payment processing services using application IDs and access tokens
Why this server?
Listed as a supported data source that can be accessed through the MCP server.
Why this server?
Listed as a supported data source that can be accessed through CData JDBC Driver and exposed via the MCP server.
Why this server?
Enables SQL-based querying of Square payment and point-of-sale data, providing access to transactions, inventory, and business analytics
Why this server?
Listed as a supported data source that can be accessed through the MCP server interface, allowing retrieval of Square data through SQL queries.
Why this server?
Provides mock integration with Square's commerce platform, demonstrating restaurant catalog management and order processing workflows for agentic commerce experiences
Why this server?
Provides access to Square payment processing and point-of-sale data, including transactions and items.
Why this server?
Allows querying live data from Square, providing read-only access to tables and columns within Square's data structure through SQL-like operations.