kintone-mcp-server-by-cdata
Provides a local, read-only MCP server that exposes Kintone data via CData’s JDBC driver as MCP tools (get tables, get columns, run SELECT queries). Designed to be run as a local stdio MCP server for clients like Claude Desktop.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS enforcement is not specified in the MCP server docs, though the underlying JDBC driver likely uses HTTPS/TLS to reach Kintone; however the MCP layer is local stdio. Authentication details and scope granularity are not described—seems to rely on JDBC/driver credentials configured in connection string/.prp. Error handling and rate limiting are not documented. .prp contains sensitive connection parameters (e.g., JdbcUrl), so protect local files and avoid logging them.
⚡ Reliability
Best When
You want local, interactive querying of Kintone data from an on-device MCP client and can install/configure the required CData JDBC driver and license.
Avoid When
You need a network-accessible API, centralized deployment, strict rate-limit/observability controls, or fine-grained authorization at the MCP layer.
Use Cases
- • Query live Kintone data from an MCP-capable desktop client without writing SQL
- • Discover available Kintone tables and columns via MCP tools
- • Answer natural-language questions over Kintone data using CData’s SQL-on-top abstraction
Not For
- • High-performance or remote multi-tenant access (stdio is local)
- • Direct full CRUD operations (README indicates this project is read-only)
- • Production services that require HTTP/REST APIs with managed networking and auth at the MCP layer
Interface
Authentication
Authentication happens through the underlying CData JDBC driver configuration (e.g., connection string builder; README notes OAuth may require browser auth). MCP server itself is configured via a local .prp file.
Pricing
Project itself is MIT-licensed, but it depends on the CData JDBC Driver which is licensed separately (README includes a license/trial step). Costs for that driver are not specified here.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio; only usable with clients running on the same machine
- ⚠ Tooling is oriented around SQL SELECT via run_query; large/unbounded queries may be slow or fail depending on driver/Kintone constraints
- ⚠ Tables/columns output is returned as CSV (first line headers), so agents must parse CSV correctly
- ⚠ OAuth may require interactive browser authentication during JDBC connection setup before running MCP server
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for kintone-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.