dolt-sql-server

Provides a SQL server interface for Dolt (MySQL-compatible wire protocol), enabling clients/tools that speak MySQL to query and interact with Dolt databases.

Evaluated Apr 04, 2026 (21d ago)
Homepage ↗ Repo ↗ Databases database sql dolt mysql-protocol server self-hosted data-versioning
⚙ Agent Friendliness
31
/ 100
Can an agent use this?
🔒 Security
46
/ 100
Is it safe for agents?
⚡ Reliability
28
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
30
Error Messages
0
Auth Simplicity
50
Rate Limits
0

🔒 Security

TLS Enforcement
60
Auth Strength
50
Scope Granularity
20
Dep. Hygiene
50
Secret Handling
50

Expected to use TLS/SSL optionally depending on server configuration; no evidence provided about mandatory TLS or secret-handling practices. Auth is likely user/password style without OAuth scopes, so authorization is probably not fine-grained at the API layer.

⚡ Reliability

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

Best When

You want to access Dolt via standard SQL clients (especially MySQL-compatible tooling) and are comfortable operating a SQL server deployment.

Avoid When

You require OAuth2/API-key web access with fine-grained scopes, or you need an HTTP/REST interface (rather than SQL) for programmatic access.

Use Cases

  • Expose Dolt databases to existing applications that use MySQL drivers
  • BI/analytics tools that expect a SQL endpoint
  • Develop/test workflows needing SQL access to versioned data (Dolt)
  • Migrate or prototype with Dolt while keeping MySQL client compatibility

Not For

  • Use as a managed cloud service (it is a self-hosted server component)
  • Cases requiring a REST/GraphQL/HTTP-first API rather than a SQL wire protocol
  • Environments needing strict enterprise auth integrations (e.g., OAuth SSO) as a primary auth model

Interface

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

Authentication

Methods: MySQL-compatible authentication over SQL protocol (credentials/configuration are typically handled server-side via Dolt/MySQL-style auth)
OAuth: No Scopes: No

No evidence of OAuth, API-key scopes, or OAuth flows. Auth is expected to be whatever the server supports in the Dolt/MySQL-compatible context (e.g., user/password).

Pricing

Free tier: No
Requires CC: No

No pricing information available; appears to be an open-source/self-hosted component.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • SQL servers often require careful handling of transactions and statements; agent attempts to treat operations as REST-style may fail.
  • Without explicit guidance, agents may not know how to authenticate/configure users for the SQL wire protocol.
  • Retry/idempotency behavior is statement-dependent (e.g., DDL/DML may not be safe to re-run).

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for dolt-sql-server.

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