linkedin-ads-mcp-server-by-cdata
Provides a local, read-only MCP server that exposes LinkedIn Ads data through a JDBC driver (CData) using MCP tools such as listing tables/columns and running SELECT queries. Designed to be used with local MCP-capable clients (e.g., Claude Desktop) via stdio.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS enforcement is not stated at the MCP layer; connection security depends on the underlying CData JDBC driver and your JDBC URL/settings. Authentication appears to rely on the JDBC driver and may involve OAuth browser-based flows, but MCP-level documentation of scopes/least-privilege is absent. The .prp file stores connection properties (including likely OAuth credentials/tokens depending on CData behavior), and the README does not describe secure storage practices (e.g., not logging tokens).
⚡ Reliability
Best When
You have a local MCP-capable desktop client and want LLM-assisted read-only exploration and querying of LinkedIn Ads data sourced via CData JDBC with your own authentication/connection string.
Avoid When
You need multi-tenant, remotely hosted access, strong built-in API rate-limit controls, or robust application-level error/retry semantics exposed by the MCP layer itself.
Use Cases
- • Query LinkedIn Ads performance/metadata from an LLM without writing SQL
- • Discovery of available tables/columns for LinkedIn Ads via MCP tools
- • Ad-hoc read-only analytics queries against LinkedIn Ads data
Not For
- • Public/remote MCP access (server is designed for local stdio use)
- • Write/update/delete operations (explicitly described as read-only in the README)
- • Use as a general-purpose SQL gateway without understanding underlying query limits/performance
Interface
Authentication
Authentication is handled indirectly through the CData JDBC driver and its connection string. The README mentions OAuth and a browser flow if the data source uses OAuth, but does not document explicit OAuth scopes at the MCP layer.
Pricing
Pricing is not described for the MCP server itself. The README indicates that the CData JDBC driver must be licensed; CData pricing is external/not specified here.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio and is intended to run on the same machine as the MCP client
- ⚠ SQL execution is delegated to the JDBC driver; incorrect or expensive queries may fail or perform poorly without MCP-level guidance
- ⚠ The tool outputs are described as CSV for metadata (tables/columns); agents may need to parse CSV carefully
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for linkedin-ads-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.