microsoft-project-mcp-server-by-cdata

Provides a local, stdio-based MCP server that exposes Microsoft Project data via tools (get_tables, get_columns, run_query) by wrapping the CData JDBC Driver for Microsoft Project, enabling LLM clients to query live project data without writing SQL.

Evaluated Apr 04, 2026 (16d ago)

Repo ↗ API Gateway mcp stdio microsoft-project cdata-jdbc llm-integration read-only

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Communicates that JDBC connections may use OAuth (InitiateOAuth=GETANDREFRESH) via connection string in a local .prp file. The MCP server itself is local/stdio, reducing network exposure, but the README does not describe secret storage hygiene, output redaction, query sanitization, or enforced least-privilege scopes. run_query effectively allows SQL execution; the README only claims read-only overall, but does not show enforcement details.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want a local MCP integration from an AI desktop client to query Microsoft Project data via a JDBC-backed relational model.

Avoid When

You require fine-grained access controls, multi-tenant hosting, or a REST/HTTP API with standard rate-limit semantics.

Use Cases

• Ask questions about Microsoft Project data (e.g., tasks/events) using an MCP-capable desktop client
• Discover available entities and fields (tables/columns) and then query them
• Run read-only SQL SELECT queries against the underlying Microsoft Project data model through MCP

Not For

• Public/remote access over the network (server is intended for local stdio use)
• Environments requiring HTTP/Webhook/hosted API access patterns
• Use cases needing full CRUD (the provided project is described as read-only)

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: CData JDBC Driver authentication (including possible OAuth) configured via JDBC connection string

OAuth: Yes Scopes: No

README indicates that if the underlying data source uses OAuth, the user must authenticate in a browser; the MCP server itself is configured via a local .prp file containing the JDBC URL (including InitiateOAuth=GETANDREFRESH).

Pricing

Free tier: No

Requires CC: No

MIT-licensed MCP server code, but JDBC driver usage requires licensing/trial according to README.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Server uses stdio, so it must run on the same machine as the MCP client
⚠ The README tool surface does not mention pagination; large result sets may be truncated depending on client/JDBC behavior
⚠ Tooling exposes a run_query capability; agents may attempt SQL beyond intended read-only patterns

Alternatives

CData Connect AI (managed MCP platform mentioned in README) CData MCP Server for Microsoft Project (managed/local full CRUD server mentioned in README) Direct integration using the CData JDBC driver from your own application (bypassing MCP)

Full Evaluation Report

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

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.