{"id":"parseplatform-parse-server","name":"parse-server","homepage":"https://hub.docker.com/r/parseplatform/parse-server","repo_url":"https://hub.docker.com/r/parseplatform/parse-server","category":"infrastructure","subcategories":[],"tags":["api","backend","parse-compatible","nodejs","express","self-hosted","rest","database"],"what_it_does":"parse-server is a Node.js/Express server that exposes a Parse-compatible backend API (e.g., for Parse-style objects, queries, file storage, and push related integrations depending on configuration). It can be used with a variety of data stores (commonly via the MongoDB adapter) to provide a REST-style Parse API.","use_cases":["Building apps that use the Parse Server/Parse SDK interface (Parse-style data models and queries).","Providing a backend for legacy Parse-based mobile/web apps.","Prototyping or maintaining Parse-compatible APIs using custom configuration and storage backends."],"not_for":["Microservices where you only need a small subset of Parse functionality.","Environments requiring managed hosting, automatic scaling, or no-infrastructure backend operation (parse-server is self-hosted).","Projects that cannot operate a Node.js/Express service and manage its dependencies and upgrades."],"best_when":"You want a Parse-compatible backend you can self-host and you already understand/need the Parse API model (and can run/maintain the Node.js service plus its database).","avoid_when":"You need a modern API contract different from the Parse protocol, or you cannot manage operational concerns (node process, DB adapter, migrations).","alternatives":["Back4App (managed Parse platform)","Parse Platform alternatives (e.g., custom REST/GraphQL backends)","LoopBack/Directus/Strapi (if Parse compatibility is not required)"],"af_score":45.8,"security_score":52.2,"reliability_score":33.8,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:49:54.912085+00:00","interface":{"has_rest_api":true,"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":["master key","session tokens / auth headers (Parse-compatible auth flows)","API keys/roles depending on configuration (Parse Server standard patterns)"],"oauth":false,"scopes":false,"notes":"Auth is Parse-compatible and typically uses a master key plus session/auth token behavior; scope granularity is not clearly documented as OAuth scopes in the provided materials."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source/self-hosted package; cost is infrastructure/operations rather than API usage pricing."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":45.8,"security_score":52.2,"reliability_score":33.8,"mcp_server_quality":0.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":15.0,"tls_enforcement":70.0,"auth_strength":60.0,"scope_granularity":20.0,"dependency_hygiene":55.0,"secret_handling":55.0,"security_notes":"As a self-hosted server, security depends on operator configuration (TLS termination, secrets management, master key exposure). Parse-compatible auth uses master key/session patterns rather than OAuth2 scopes, so least-privilege is more manual.","uptime_documented":10.0,"version_stability":55.0,"breaking_changes_history":40.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"offset/limit style (Parse queries commonly use limit/skip)","retry_guidance_documented":false,"known_agent_gotchas":["Parse Server behavior depends heavily on configuration (database adapter, auth/master key settings, cloud code hooks).","Idempotency is not generally guaranteed for generic write endpoints; agents should avoid naive retries for non-idempotent mutations.","Rate limiting and backoff behavior are not clearly standardized/documented for agents without checking the deployed configuration."]}}