{"id":"dolthub-dolt-sql-server","name":"dolt-sql-server","homepage":"https://hub.docker.com/r/dolthub/dolt-sql-server","repo_url":"https://hub.docker.com/r/dolthub/dolt-sql-server","category":"databases","subcategories":[],"tags":["database","sql","dolt","mysql-protocol","server","self-hosted","data-versioning"],"what_it_does":"Provides a SQL server interface for Dolt (MySQL-compatible wire protocol), enabling clients/tools that speak MySQL to query and interact with Dolt databases.","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"],"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.","alternatives":["Dolt CLI / SQL over direct Dolt connections (if applicable in your environment)","Deploy a MySQL-compatible proxy/adapter in front of Dolt (if supported by your architecture)","Use Dolt-specific clients/libraries (where available) instead of running a SQL server gateway"],"af_score":31.0,"security_score":46.0,"reliability_score":27.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:40:45.958470+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["MySQL-compatible authentication over SQL protocol (credentials/configuration are typically handled server-side via Dolt/MySQL-style auth)"],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information available; appears to be an open-source/self-hosted component."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":31.0,"security_score":46.0,"reliability_score":27.5,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":50.0,"scope_granularity":20.0,"dependency_hygiene":50.0,"secret_handling":50.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":30.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_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)."]}}