{"id":"cdatasoftware-activecampaign-mcp-server-by-cdata","name":"activecampaign-mcp-server-by-cdata","homepage":null,"repo_url":"https://github.com/CDataSoftware/activecampaign-mcp-server-by-cdata","category":"api-gateway","subcategories":[],"tags":["mcp","activecampaign","cdata","jdbc","local-stdio","read-only","data-access"],"what_it_does":"A locally hosted, read-only MCP server that exposes ActiveCampaign data through CData's JDBC Driver as simple MCP tools (get tables, get columns, run SELECT queries). It runs as a stdio process on the same machine as the MCP client (e.g., Claude Desktop) and uses a provided .prp configuration to point to the JDBC driver and connection details.","use_cases":["Let an LLM query live ActiveCampaign data without writing SQL","Discovery of available tables/columns in the ActiveCampaign dataset via tools","Analytics-style questions using SELECT queries over exposed relational models","Local agent integrations where the client can run on the same host"],"not_for":["Exposing an internet-reachable API endpoint for remote clients","Full CRUD or write/update/delete operations (advertised as read-only in this project)","Environments that require built-in pagination controls or cursor-based result handling"],"best_when":"You want a local MCP-capable assistant to query ActiveCampaign data on the same machine using a preconfigured JDBC connection.","avoid_when":"You need robust authentication/session management for remote access, strong documented rate-limit behavior, or highly controlled query safety (since the interface includes arbitrary SELECT SQL execution).","alternatives":["CData's managed/more complete MCP offering (CData Connect AI / CData MCP Server for ActiveCampaign) if remote access and write capabilities are required","Direct use of the CData ActiveCampaign JDBC driver from your own application (without MCP)","A custom MCP server wrapper around the ActiveCampaign API with tighter query/field controls"],"af_score":48.5,"security_score":40.5,"reliability_score":21.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T20:00:21.338497+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":["JDBC driver connection using configured OAuth/credentials inside the JDBC connection string and/or .prp file"],"oauth":true,"scopes":false,"notes":"Authentication is delegated to the CData JDBC Driver. The README notes that OAuth may require browser-based authentication for the connection string; specific scopes/permissions are not described in this MCP server README."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing for the MCP server itself is provided; the CData JDBC driver requires licensing as described in the setup."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":48.5,"security_score":40.5,"reliability_score":21.2,"mcp_server_quality":70.0,"documentation_accuracy":60.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":5.0,"tls_enforcement":40.0,"auth_strength":55.0,"scope_granularity":30.0,"dependency_hygiene":45.0,"secret_handling":30.0,"security_notes":"The MCP server runs locally over stdio (reducing network exposure), but the README provides little detail about how errors are handled or how sensitive connection strings/secrets are protected in logs. Authentication details are delegated to the CData JDBC driver; the README mentions OAuth may be required but does not document fine-grained scopes. The presence of a generic run_query tool that executes provided SQL increases risk of accidental over-broad data access if the agent constructs unsafe/expensive queries. No explicit TLS, secret redaction, or rate-limit handling behavior is documented in the MCP server README.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"true","idempotency_notes":"The exposed MCP tools are primarily read/discovery (get_tables/get_columns/run_query SELECT), which are naturally idempotent. No explicit idempotency guidance is provided for the MCP tool calls.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Server uses stdio, so it must run on the same machine as the MCP client.","Arbitrary SQL is executed via run_query (SELECT), so the agent should avoid overly broad queries to reduce load and output size.","Claude Desktop may need a full restart to pick up newly configured MCP servers.","Tool outputs are returned in CSV; agents may need to parse/interpret CSV correctly."]}}