database · inferred from evidence
A database system from which incremental syncs were failing due to offset issues.
Incremental syncs from MongoDB to Postgres kept failing with `java.lang.IllegalArgumentException: Saved offset is not valid`. The sync would then retry from a full refresh, which was expensive on a large collection. A community member trace
Shows how to fix mongoDB Atlas: connect from AWS Lambda and Vercel without pool exhaustion. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Fixes MongoDB MCP write tools failing with not authorized or read-only errors when the server was started with --readOnly. The flag is in the default config examples and silently disables all write tools. The fix is removing --readOnly when
Fixes confusion between the MongoDB MCP server's two auth modes: connection string vs Atlas API service-account credentials. Setting MDB_MCP_API_CLIENT_ID without completing the Atlas API access setup fails, and mixing both modes causes con
Fixes the MongoDB MCP server failing to connect when the database password contains special characters. Characters like @, /, ? and # break connection-string parsing and must be percent-encoded. Use when valid credentials are rejected with
Shows how to fix mongoDB Atlas: size the connection pool deliberately. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Guide vectorSearch must be the first pipeline stage; a wrong index name returns empty results: Verify the index exists with the exact name before debugging query vectors: a wrong name gives empty results, not an error. Use this when you hit