instagram-mcp-server-by-cdata

Provides a local, read-oriented MCP Server that exposes Instagram data as relational tables via CData’s JDBC Driver, wrapped behind a small MCP tool surface (get tables/columns and run SELECT queries) for LLM clients such as Claude Desktop.

Evaluated Apr 04, 2026 (16d ago)
Repo ↗ Ai Ml mcp instagram jdbc cdata local-stdio read-only ai-integration
⚙ Agent Friendliness
53
/ 100
Can an agent use this?
🔒 Security
31
/ 100
Is it safe for agents?
⚡ Reliability
32
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
80
Documentation
70
Error Messages
0
Auth Simplicity
55
Rate Limits
5

🔒 Security

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

Communication is local (stdio) rather than over HTTPS/TLS; the README does not describe transport-layer security or how secrets in connection strings are protected from logs. Authentication and authorization granularity are not specified by the MCP server; they depend on the CData JDBC Driver and Instagram/OAuth behavior. No dependency/SBOM/CVE posture is provided in the provided content.

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
50
Error Recovery
30
AF Security Reliability

Best When

You run the MCP server locally on the same host as your MCP-capable desktop client and need to inspect/query Instagram data with low friction.

Avoid When

You need a public hosted service, multi-region reliability guarantees, or fine-grained programmatic control over auth/rate limits/error codes beyond what the underlying JDBC driver provides.

Use Cases

  • Query Instagram-related datasets with natural-language questions (no manual SQL for end users)
  • Explore available Instagram tables and columns programmatically through MCP tools
  • Run read-only SELECT queries over Instagram data via a consistent MCP interface

Not For

  • Secure, remote multi-tenant access over a network (the server uses stdio and is intended for same-machine clients)
  • Production-grade API access with documented SLAs and rate-limit contracts
  • Robust CRUD workflows where non-read operations are required

Interface

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

Authentication

Methods: JDBC driver authentication as configured in the CData JDBC connection string / .prp file OAuth via browser (mentioned as required when the data source uses OAuth)
OAuth: Yes Scopes: No

Authentication is delegated to the CData JDBC Driver configuration; the MCP server itself is started via a local .prp file and does not describe its own auth mechanisms or scope model.

Pricing

Free tier: No
Requires CC: No

Repository is MIT-licensed, but JDBC driver licensing is required (README instructs to license the CData JDBC Driver). Pricing for the driver/platform is not described in the README.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Uses stdio; only works with clients running on the same machine
  • Tool arguments require correct table names/column selection; incorrect SQL/table names may produce JDBC/SQL-layer errors
  • Claude Desktop may require fully quitting and restarting to pick up newly added MCP servers

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for instagram-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