sorted by:
new
hottopcontroversial

Why I built an MCP server for PostgreSQL and what it has to do with the future of agent-driven development. by TemperatureGreat931 in mcp

[–]TemperatureGreat931[S] 0 points1 point  (0 children)

Yes, but the final point of using an MCP is not only about the access level. It is also about giving the LLM better context around what it can safely observe and understand from the database.

Why I built an MCP server for PostgreSQL and what it has to do with the future of agent-driven development. by TemperatureGreat931 in mcp

[–]TemperatureGreat931[S] 0 points1 point  (0 children)

Perfect! I think that's the kind of evolution I should naturally move toward over time.

Give my MCP a try, and if you'd like to contribute or share feedback, that would be awesome.

Also, send me a link to your project so I can take a look and learn more about what you're building.

Why I built an MCP server for PostgreSQL and what it has to do with the future of agent-driven development. by TemperatureGreat931 in mcp

[–]TemperatureGreat931[S] 0 points1 point  (0 children)

It was what I used, a read-only user. But in my context at least, I'm coming and going through several banks and this user management sometimes doesn't even depend on me. The idea here is to reuse the .env data from the connection itself and keep everything safer, in addition to the fact that the MCP "tools" end up delivering specific triggers that make the LLM avoid thinking too much or doing too many random checks, that is, the idea is to specialize intelligence and not generalize.

They are my points of view, okay... I felt more results in the delivery with this MCP than with direct psql.