{"id":"percona-percona-server","name":"percona-server","homepage":"https://hub.docker.com/r/percona/percona-server","repo_url":"https://hub.docker.com/r/percona/percona-server","category":"databases","subcategories":[],"tags":["databases","mysql-compatible","self-hosted","oltp","replication","performance-tuning"],"what_it_does":"Percona Server for MySQL is a database server distribution (a MySQL-compatible fork) focused on performance, scalability, and operational features such as advanced monitoring/tuning and (depending on version) additional storage/replication improvements.","use_cases":["Running MySQL workloads with performance and operational enhancements","Production OLTP databases that benefit from Percona-specific tuning and tooling","Self-managed MySQL-compatible clusters and replication setups","Performance troubleshooting and database engineering where source-level customization is acceptable"],"not_for":["Serverless/no-ops environments where managing a full database instance is not feasible","Use cases requiring a strict managed DB SLA without operational responsibility","Agent-driven APIs/automation expecting a modern HTTP/REST interface for direct database operations"],"best_when":"You need a self-hosted, MySQL-compatible database and can manage database ops (backups, upgrades, tuning).","avoid_when":"You need a simple developer-facing SaaS/API product rather than an infrastructure component to deploy and operate.","alternatives":["MySQL Community Server (Oracle)","MariaDB","Amazon RDS for MySQL / Aurora MySQL (managed alternatives)","Google Cloud SQL for MySQL"],"af_score":27.5,"security_score":55.8,"reliability_score":37.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:49:31.593223+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":["Database authentication (e.g., MySQL user accounts/credentials) via client connections"],"oauth":false,"scopes":false,"notes":"Database-level authentication/authorization is configured within MySQL/Percona (users, privileges). There is no separate product-level OAuth/API scope model described here."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source distribution; cost depends on your infrastructure and operational effort. This evaluation does not assume any paid Percona offerings."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":27.5,"security_score":55.8,"reliability_score":37.5,"mcp_server_quality":0.0,"documentation_accuracy":35.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":60.0,"rate_limit_clarity":0.0,"tls_enforcement":70.0,"auth_strength":60.0,"scope_granularity":40.0,"dependency_hygiene":45.0,"secret_handling":60.0,"security_notes":"Security is primarily determined by database configuration (accounts/privileges), transport security (TLS settings), and how credentials are managed in your deployment/clients. As evaluated here from limited package-level context, there is no specific evidence of strong product-level secret-handling or fine-grained API scope controls.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":50.0,"error_recovery":45.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is an infrastructure/database package, not an agent-callable HTTP API; automation requires DB client connections and careful transaction/idempotency design.","Operational tasks (migrations, upgrades, replication changes) can be stateful and may require maintenance windows and rollback plans.","Database errors and failure modes vary by workload/config; agent retry behavior needs domain-specific safety checks (e.g., avoiding duplicate writes)."]}}