azure-devops-mcp-server-by-cdata
Provides a local, read-only MCP server that wraps the CData JDBC Driver for Azure DevOps, exposing Azure DevOps entities as SQL-accessible “tables” and making them available to MCP clients (e.g., Claude Desktop) via tool calls like get_tables, get_columns, and run_query over stdio.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS: the server is local stdio and does not specify transport security details; JDBC/OAuth transport security is handled by underlying driver but not described here. Auth: authentication is delegated to JDBC driver; OAuth is mentioned but the MCP server does not document its own auth model or enforcement. Scopes: no explicit scope model described. Secret handling: secrets are likely stored in the .prp/JdbcUrl, but the README does not address logging/redaction. Dependency hygiene: no vulnerability/dependency policy or SBOM provided in the README.
⚡ Reliability
Best When
You want an on-machine MCP integration for read-oriented Azure DevOps querying using a known JDBC driver, primarily from a local MCP-capable desktop client.
Avoid When
You need network-accessible MCP, strong operational guarantees (SLA/status), or you require fine-grained, well-documented security controls/limits in the MCP server itself.
Use Cases
- • Ask questions about live Azure DevOps data in an AI client without writing SQL
- • Discover available Azure DevOps “tables” and columns via MCP tools
- • Run SELECT queries against Azure DevOps via an MCP tool interface
Not For
- • Direct remote MCP access over the network (stdio implies same-machine use)
- • Use cases requiring a fully managed cloud MCP endpoint
- • Use cases needing a documented REST/HTTP interface, webhooks, or SDK-based integration
- • Production-grade write/update/delete via MCP (README characterizes this project as read-only; broader CRUD is noted elsewhere as a separate managed option)
Interface
Authentication
Authentication is delegated to the underlying CData JDBC driver configuration. The README notes that OAuth may require browser-based authentication when building the connection string. MCP server auth mechanisms (e.g., token-based auth) are not described.
Pricing
Pricing not described for the MCP server itself. The CData JDBC driver appears to require licensing (trial or license key), but cost details are not provided in the README.
Agent Metadata
Known Gotchas
- ⚠ Server uses stdio, so it can only be used with clients running on the same machine as the server
- ⚠ No explicit rate limiting information is provided
- ⚠ Tool outputs are returned in CSV for get_tables/get_columns; agents may need to parse CSV reliably
- ⚠ OAuth authentication may be required during connection string setup, potentially involving interactive browser steps
- ⚠ Because this server wraps a JDBC driver and runs SQL, agents may need to avoid unsafe SQL patterns (even if intended use is SELECT)
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for azure-devops-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.