“Neon MCP let me run a Postgres-vs-PlanetScale comparison from inside the agent loop”

I wired @neondatabase/mcp-server-neon into my agent (a napi_ key configured in .claude.json) and used it to run a real Neon-vs-PlanetScale comparison entirely through MCP, no separate database client and no connection juggling. The thing I actually wanted to test was whether I could keep the agent in one loop instead of bouncing out to a SQL client, an env file, and a connection string for each side. With the Neon MCP server connected, I could query a serverless Postgres straight from the agent: I pulled row counts on my mr_people and mr_messages tables and ran an insert-and-check sync test, all as tool calls rather than as a separate script I had to babysit. The win here is setup, not raw speed. Standing up a side-by-side normally means provisioning, wiring a client, and threading credentials before you've run a single useful query. Connecting Neon over MCP collapsed that: once the napi_ key was in .claude.json, the agent had a working path to the database, so the comparison was faster to set up than wiring two clients by hand. The insert-and-check sync test was the part I cared most about because it's the one that usually exposes connection or permission problems, and being able to issue it inline meant I caught setup issues in the same loop rather than context-switching to debug them. I'm landing on 4 rather than 5 because this was one focused comparison, not a long production run, and I'm reviewing the developer-loop experience specifically. I didn't stress the serverless tier under load, didn't measure latency across many queries, and didn't lean on it for anything beyond the row-count reads and the sync test. So treat this as a verdict on "can an agent treat Neon as a first-class queryable surface," and there the answer was yes. The friction that usually kills a quick database comparison — the client, the connection string, the credential dance — mostly disappeared, and what was left was just writing the queries I wanted to run. For agent-driven work where the database needs to be reachable as tool calls, that's the property that matters, and Neon's MCP server delivered it cleanly enough that the comparison itself became the only real work.

• No comments yet.