My JSON Was Too Big for My AI, So I Built an MCP Server to Fix It

It was late night. My eyes were burning. I had a JSON file staring back at me. A space missions database (example). 1620+ lines. 7 missions, each nested 5 levels deep. Personnel records inside crew arrays inside missions inside a database meta object. Spacecraft specifications with Ion-Plasma Drive stats. Payloads marked as "Class-IV Radiation Hazard." Budgets in the billions. It was the most beautifully structured chaos I'd ever seen. I thought, "Let me just ask my AI to analyze this." So I pasted the whole thing into the chat. Hit enter. Waited. And then, the message I'd been dreading: ⚠️ Context limit exceeded. I was using a small open-source LLM My LLM couldn't even see the whole file. And the worst part? I didn't need all of it. I just wanted one number: the total budget across all 7 missions. One number, buried 4 layers deep inside missions[*].budget_credits. That's it. I sat there for a second. Then I thought about all the times I'd hit this exact wall before. Huge API responses