surveymonkey-mcp-server-by-cdata
A locally hosted, read-only MCP server that exposes SurveyMonkey data via CData’s JDBC Driver as MCP tools (get tables, get columns, run SQL SELECT queries). It’s intended for use with MCP-capable desktop clients (e.g., Claude Desktop) and requires local configuration using a .prp file that points to the CData JDBC driver and connection/JDBC URL (including OAuth parameters if used).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Local stdio transport reduces remote exposure, but the README does not document TLS/networking behavior for the MCP server itself (stdio implies local IPC). Authentication is delegated to the CData JDBC driver using OAuth parameters in the JDBC URL; the MCP layer does not document fine-grained scopes or authorization controls. The .prp file likely contains sensitive JDBC connection information; the README does not describe how secrets should be stored securely or how logging is handled. Dependency health (Java/Maven deps) and vulnerability status are not provided in the supplied content.
⚡ Reliability
Best When
You need local, agent-to-data querying on a single machine where the MCP host (Claude Desktop or similar) can launch the MCP server and you already have CData JDBC Driver credentials/licensing configured.
Avoid When
You need multi-tenant or remote access, strong built-in authorization at the MCP layer, or you cannot secure/manage OAuth/JDBC credentials on the same host.
Use Cases
- • Ask an LLM natural-language questions about SurveyMonkey data without writing SQL
- • Explore available SurveyMonkey-related tables/columns via MCP tools
- • Run read-only analytics/reporting queries (SELECT) against SurveyMonkey through the MCP interface
Not For
- • Direct public/remote hosting of an MCP endpoint (it uses stdio for local-only client communication)
- • Applications needing full CRUD or write/update/delete operations (server is described as read-only)
- • Use cases requiring a dedicated HTTP/REST API for programmatic access from other machines
Interface
Authentication
Auth is handled by the underlying CData JDBC driver/connection string. README explicitly notes that if the data source uses OAuth, authentication occurs in a browser. The README does not describe fine-grained permission scopes at the MCP layer.
Pricing
Pricing/licensing for the MCP server itself isn’t detailed in README; CData JDBC Driver licensing is required via a --license command, which likely implies paid licensing depending on usage.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it only works with MCP clients on the same machine that can launch/connect to the server process
- ⚠ Requires correct local .prp configuration including DriverPath/DriverClass/JdbcUrl and (if OAuth is required) browser-based authentication flow
- ⚠ Tool outputs for get_tables/get_columns are returned as CSV; agents may need to parse CSV reliably
- ⚠ README example references Salesforce.prp in the run command, which may be confusing when setting up for SurveyMonkey
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for surveymonkey-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.