square-mcp-server-by-cdata
Provides a local, read-only MCP server that exposes Square data as queryable tables/columns via a wrapped CData JDBC Driver. It runs as an MCP stdio server intended for use with local MCP clients (e.g., Claude Desktop) to retrieve live Square data without requiring users to write SQL.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Runs locally via stdio (reduces network exposure) but relies on JDBC driver configuration and OAuth/token material captured in the connection string/.prp file. The README does not discuss secret storage practices (e.g., file permissions), token handling, logging redaction, or MCP-side authorization. OAuth complexity is delegated to the JDBC driver connection utility. No explicit TLS/network transport settings apply at the MCP boundary since it is stdio-local.
⚡ Reliability
Best When
You have a local MCP-capable client (Claude Desktop) and want to query Square data from a local machine using a JDBC-to-relational mapping without building custom database connectors.
Avoid When
You need network-accessible deployment, centralized authentication, documented SLAs, or robust rate-limit/error-contract guarantees at the MCP layer.
Use Cases
- • Answering natural-language questions about Square data (e.g., open items, transactions, events)
- • Exploring available tables and columns for Square datasets via MCP tools
- • Running read-only SQL SELECT queries against Square data mapped through the CData JDBC driver
- • Integrating Square data retrieval into local LLM workflows where stdio-based MCP is supported
Not For
- • Providing a secure multi-tenant or internet-exposed service (stdio is local-only)
- • User-facing production APIs requiring strong API gateway features (auth/rate limiting/auditing)
- • Full CRUD operation (server is described as read-only; tools shown include get_tables/get_columns/run_query)
Interface
Authentication
The README indicates that if the Square data source uses OAuth, authentication happens in a browser via the JDBC connection string utility. MCP itself appears to rely on the locally configured JDBC connection string stored in the .prp file.
Pricing
Pricing for the MCP server/package is not specified in the provided README content. The CData JDBC driver requires licensing/trial/license key as described.
Agent Metadata
Known Gotchas
- ⚠ Server is stdio-based and 'can only be used with clients that run on the same machine as the server'.
- ⚠ Tool naming uses a server prefix (servername) in tool names (e.g., {servername}_run_query); callers must use the configured server name/prefix correctly.
- ⚠ The .prp file must include correct JDBC DriverPath/DriverClass/JdbcUrl and optional Tables filtering; missing/incorrect configuration will prevent successful tool operations.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for square-mcp-server-by-cdata.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.