{"id":"cdatasoftware-acumatica-mcp-server-by-cdata","name":"acumatica-mcp-server-by-cdata","homepage":null,"repo_url":"https://github.com/CDataSoftware/acumatica-mcp-server-by-cdata","category":"infrastructure","subcategories":[],"tags":["mcp","stdio","jdbc","acumatica","cdata","read-only","local-integration","ai-data-access"],"what_it_does":"Provides a local, read-only MCP (Model Context Protocol) server that exposes Acumatica data via CData JDBC driver models. It supports MCP tool calls for listing tables/columns and running SQL SELECT queries against the Acumatica backend.","use_cases":["Ask an AI client to retrieve live Acumatica data without writing SQL","Discover available Acumatica tables/columns via MCP tools","Run ad-hoc read-only SQL SELECT queries through an MCP stdio connection for reporting/analysis"],"not_for":["Operations requiring write/create/update/delete (explicitly described as read-only in this project)","Use cases needing a remotely hosted MCP endpoint (server uses stdio and is intended for same-machine clients)","Environments that require strong service-level guarantees (no SLA or uptime/status info provided)","Data governance models requiring strict query safety/guardrails beyond what the underlying JDBC driver enforces"],"best_when":"You want a local MCP integration for read-heavy analytics/questions against Acumatica, using the CData JDBC Driver as the underlying connector.","avoid_when":"You need web-accessible remote access, multi-tenant isolation, fine-grained authorization per tool/user, or robust documented retry/idempotency behavior.","alternatives":["CData managed MCP platform (CData Connect AI) for remote access","CData’s other Acumatica MCP server product advertised for full CRUD (per README)","Direct integration using the CData JDBC driver and your own SQL/BI tooling"],"af_score":43.5,"security_score":37.2,"reliability_score":13.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:49:47.269149+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["CData JDBC connection/auth as configured in the JDBC driver and .prp file (including possible OAuth flow initiated in browser, if the underlying data source uses OAuth)"],"oauth":true,"scopes":false,"notes":"README indicates that if the data source uses OAuth, authentication may be required in a browser when testing the connection. The MCP server itself is local stdio; authentication responsibility appears to be delegated to the JDBC driver configuration via the .prp/JdbcUrl properties."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":["CData JDBC Driver licensing (explicit licensing step in README)","Potential managed MCP offerings (mentioned for remote/full CRUD)"],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Project code is MIT licensed, but it depends on the CData JDBC Driver, which requires licensing per README. No MCP-server pricing details or credit card requirement are stated here."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":43.5,"security_score":37.2,"reliability_score":13.8,"mcp_server_quality":70.0,"documentation_accuracy":65.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":45.0,"scope_granularity":10.0,"dependency_hygiene":40.0,"secret_handling":30.0,"security_notes":"Security depends heavily on the underlying CData JDBC driver and how the .prp/JdbcUrl is provided. This README does not describe TLS requirements, transport security between MCP client/server (stdio is local), logging behavior, secret storage practices, or fine-grained authorization. Tooling exposes the ability to run SQL SELECT via MCP, which can still risk data exposure if the connected credentials have broad permissions.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":0.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"Only read-oriented tools are described (get_tables, get_columns, run_query with SELECT). Idempotency is likely natural for SELECT, but no explicit guidance is provided for retries or semantics.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Server uses stdio; only usable with clients running on the same machine.","Run-time tool availability depends on .prp configuration (tables list/prefix/server name/version) and the CData JDBC driver licensing/auth state.","Tool outputs described as CSV; agents must parse CSV reliably from tool results.","No explicit rate limit/error-code guidance is documented for the MCP layer (and underlying JDBC constraints may surface as tool failures)."]}}