Ajay Kulkarni

the Postgres context it needs, best practices, documentation, so that it's instantly like an expert developer.

No, it's a great point.

And I think, and again, like, hey, is MCP going to be the end-all protocol?

I don't know.

But there will be a protocol.

And I think that's the point, right?

That's the point you're making, the point I'm trying to make.

And why do you need this protocol?

Well, number one, you need a way for the agents to interact with your APIs.

But number two, you probably want to give them access without giving them the full keys to the kingdom.

You want to give your agent just enough power, but maybe sandbox in a certain way.

Maybe they can do some things, but not others.

And I think this is where MCP or agentic APIs really play a role.

And then the CLI is another way to do that.

CLI is another way to give essentially a tool to the agent.

that is properly defined and what it can and can't do.

Yeah, no, I think it's really interesting.

I think the team's done some really cool.

I think this docs thing, and I'm not sure if I'm beating a dead horse here, but I think what they did with the docs I thought was especially clever that I haven't seen anyone else do.

It's like, hey, we have an MCP server where we have indexed the Postgres documentation and the Tiger documentation.