adobe-analytics-mcp-server-by-cdata

Provides a local, read-only MCP server that wraps CData’s JDBC Driver for Adobe Analytics, exposing Adobe Analytics data as MCP tools (get_tables, get_columns, run_query) for LLM clients (e.g., Claude Desktop) to query live data without writing SQL.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp adobe-analytics data-access jdbc local-stdio llm-tools
⚙ Agent Friendliness
48
/ 100
Can an agent use this?
🔒 Security
35
/ 100
Is it safe for agents?
⚡ Reliability
28
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
78
Documentation
72
Error Messages
0
Auth Simplicity
55
Rate Limits
0

🔒 Security

TLS Enforcement
20
Auth Strength
55
Scope Granularity
10
Dep. Hygiene
40
Secret Handling
45

Security relies primarily on the underlying CData JDBC driver and configured JDBC/OAuth mechanisms; this MCP server’s own security controls (authn/authz, least-privilege scopes, TLS requirements, audit logging) are not described. Because it is a local stdio process, transport-level concerns shift to local host security; however, the README does not document how secrets are stored or whether they could appear in logs/errors.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
40
Error Recovery
25
AF Security Reliability

Best When

You want a local, tool-based bridge from an MCP-capable desktop client to Adobe Analytics data using an installed CData JDBC driver.

Avoid When

You need fine-grained row/column security, centralized access controls, or a network-accessible API with published SLAs and operational tooling.

Use Cases

  • Ask natural-language questions about Adobe Analytics data
  • Explore available datasets/tables and schema via tools
  • Run ad-hoc SQL SELECT queries against Adobe Analytics through an MCP-enabled client

Not For

  • Use as a hosted/remote public API endpoint (server uses stdio and is intended for same-machine clients)
  • Directly managing/modifying Adobe Analytics data (the MCP server described is read-only)
  • Production environments requiring strict availability guarantees without monitoring/SLA

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: CData JDBC driver licensing via java -jar ... --license Connection authentication handled by the underlying CData JDBC driver (may use OAuth depending on configuration)
OAuth: Yes Scopes: No

The MCP server itself is configured via a local .prp that includes the JDBC URL/connection string. The README notes OAuth may be required for some data sources; exact scopes and scope granularity are not described here.

Pricing

Free tier: No
Requires CC: No

Pricing is not provided for this MCP server; it depends on CData JDBC driver licensing and possibly Adobe Analytics access.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • The server uses stdio, so it must be run on the same machine as the MCP client.
  • Large/unbounded SELECT queries may be slow or costly, but the README does not document limits or guidance.
  • The tools return CSV; agents may need to parse CSV results carefully.
  • Tool naming relies on a Prefix/ServerName in the .prp file; incorrect configuration will lead to missing tools.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for adobe-analytics-mcp-server-by-cdata.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered