{"id":"cdatasoftware-sap-ariba-procurement-mcp-server-by-cdata","name":"sap-ariba-procurement-mcp-server-by-cdata","homepage":null,"repo_url":"https://github.com/CDataSoftware/sap-ariba-procurement-mcp-server-by-cdata","category":"devtools","subcategories":[],"tags":["mcp","stdio","jdbc","sap-ariba","data-access","read-only","local-integration"],"what_it_does":"Provides a local, stdio-based MCP server wrapper around the CData JDBC Driver for SAP Ariba Procurement, exposing available tables/columns and a SQL SELECT query tool to an MCP-capable client (e.g., Claude Desktop). The server is described as read-only in this repo.","use_cases":["Query live SAP Ariba Procurement data using natural-language questions (via an MCP client) without writing SQL","Exploratory browsing of available tables and columns","Running read-only SELECT queries for reporting/analysis"],"not_for":["Use cases requiring internet-reachable (remote) MCP access (the MCP server is local/stdio)","Use cases requiring full CRUD or non-SELECT mutations through this specific MCP server","Environments that require strong governance around arbitrary SQL text execution without constraints"],"best_when":"You have a local desktop workflow (same machine) and want an agent to query SAP Ariba Procurement data through an MCP client using CData JDBC connectivity.","avoid_when":"You need strict multi-tenant network isolation, remote access over the network, or guaranteed prevention of overly broad/expensive queries; also avoid when you cannot manage credentials that will be used by the JDBC driver.","alternatives":["CData’s managed “CData Connect AI” (as referenced in the README)","CData’s full MCP server for SAP Ariba Procurement (read/write/update/delete) as referenced in the README","Direct integration via the CData JDBC Driver and your own query layer (rather than MCP)"],"af_score":50.0,"security_score":50.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:19.200183+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 license activation (local java -jar ... --license)","OAuth authentication if the underlying data source/connection uses OAuth (noted during connection string setup)","Credentials supplied via CData JDBC connection string stored in a .prp file (including OAuth parameters like InitiateOAuth=GETANDREFRESH per example)"],"oauth":true,"scopes":false,"notes":"This MCP server itself is local; authentication is handled by the underlying CData JDBC driver during JDBC connection string setup/execution. The README implies OAuth may be involved but does not specify OAuth scopes or explicit least-privilege options."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing for the CData JDBC driver and any related managed platforms is not provided in the README; this evaluation cannot confirm costs from the supplied content."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":50.0,"security_score":50.2,"reliability_score":13.8,"mcp_server_quality":78.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":10.0,"tls_enforcement":85.0,"auth_strength":55.0,"scope_granularity":20.0,"dependency_hygiene":50.0,"secret_handling":40.0,"security_notes":"Strengths: Communication between MCP client and server is local (stdio) per README, reducing network exposure. The actual data transport security depends on the underlying CData JDBC driver’s implementation (not described here). Weaknesses/risks: credentials/connection strings are placed into a local .prp file and may include OAuth initiation parameters; the repo does not describe redaction/logging behavior, least-privilege scopes, or how errors/results are sanitized. Generic SQL execution increases the risk of data overexposure or performance issues if the agent forms unsafe queries.","uptime_documented":0.0,"version_stability":35.0,"breaking_changes_history":0.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"The exposed tools include running SQL SELECT queries; those are typically idempotent, but the repo text also mentions general read/write/update/delete in other contexts. No explicit idempotency guarantees or safe retry semantics are documented for the MCP tools themselves.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["The server uses stdio, so it must run on the same machine as the MCP client (not suitable for remote/network MCP usage).","The tool includes a generic run_query SQL interface; agents may generate expensive or overly broad queries unless you constrain prompts or query patterns.","The README example mentions Salesforce in the .prp command example path, which may confuse setup if copied verbatim (check you’re using the correct .prp for SAP Ariba Procurement)."]}}