<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Monghoul blog</title><description>Writing about MongoDB from the people building a MongoDB IDE. Query plans, schema cost, and what the server actually does on your version.</description><link>https://monghoul.com/</link><language>en-us</language><item><title>What a MongoDB MCP server can reach, before you point one at production</title><link>https://monghoul.com/blog/mongodb-mcp-server-scope/</link><guid isPermaLink="true">https://monghoul.com/blog/mongodb-mcp-server-scope/</guid><description>The official server writes unless you pass --readOnly, its confirmations depend on the client supporting elicitation, and its Atlas tools create users.</description><pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate></item><item><title>What each MongoDB release added to the aggregation language, from 5.0 on</title><link>https://monghoul.com/blog/aggregation-stages-by-version/</link><guid isPermaLink="true">https://monghoul.com/blog/aggregation-stages-by-version/</guid><description>The answer to &quot;why does $percentile not work&quot; is almost always the server version. Here is what arrived in each release from 5.0 to 8.3.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>The 100 MB aggregation limit stopped failing your query in MongoDB 6.0</title><link>https://monghoul.com/blog/allow-disk-use-by-default/</link><guid isPermaLink="true">https://monghoul.com/blog/allow-disk-use-by-default/</guid><description>Most guides say a stage over 100 MB errors unless you pass allowDiskUse. That has been wrong since MongoDB 6.0, and the new failure is quiet.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>BSONObjectTooLarge, and the field that is actually costing you the space</title><link>https://monghoul.com/blog/bsonobjecttoolarge/</link><guid isPermaLink="true">https://monghoul.com/blog/bsonobjecttoolarge/</guid><description>The 16 MB limit is on the encoded document, not on what you think you stored. The usual culprit is an array nobody bounded.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Extended JSON, and where $date and $oid quietly change your data</title><link>https://monghoul.com/blog/extended-json-pitfalls/</link><guid isPermaLink="true">https://monghoul.com/blog/extended-json-pitfalls/</guid><description>JSON has no date type and no 64-bit integer. Extended JSON has both, in two modes, and relaxed mode loses less than people think and more than they check.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>A compound index in the wrong order is a sort you did not ask for</title><link>https://monghoul.com/blog/index-field-order/</link><guid isPermaLink="true">https://monghoul.com/blog/index-field-order/</guid><description>The same three fields in a different order decides whether the index serves your sort or the server does it in memory. The plan says which you have.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Your query uses an index and is still slow</title><link>https://monghoul.com/blog/indexed-and-still-slow/</link><guid isPermaLink="true">https://monghoul.com/blog/indexed-and-still-slow/</guid><description>An IXSCAN in the plan is not the finish line. The number that matters is how many documents the server had to read to return the ones you asked for.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>$lookup against embedding, measured on 10 million documents</title><link>https://monghoul.com/blog/lookup-vs-embedding-measured/</link><guid isPermaLink="true">https://monghoul.com/blog/lookup-vs-embedding-measured/</guid><description>A $lookup on an indexed key cost nothing here. Sorting on the joined field cost nine seconds. The gap between those two is the whole decision.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Read-only MongoDB access for an AI agent, and what still gets through</title><link>https://monghoul.com/blog/mongodb-mcp-read-only/</link><guid isPermaLink="true">https://monghoul.com/blog/mongodb-mcp-read-only/</guid><description>A read-only flag that works by reading the query text can be walked past in four lines. Where the check runs matters more than what it is called.</description><pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate></item></channel></rss>