Ajay Kulkarni

What, 15 years, maybe more?

I mean, I don't know.

If you look at Unix, maybe it's forever, you know?

I think the key thing is the CLI is a clear program that agents can use.

So when we built our Tiger CLI, it's written in Go.

It's distributed as a single binary.

It essentially provides a unified control plane for your database on Tiger Cloud.

And so it covers auth, obviously, creating, starting, stopping, forking databases, connecting databases.

But what's really, I think, nice about it, like you pointed out, is that it has MCP baked in.

So you can run, essentially, a local MCP server through the CLI that then your cloud code or whatever can talk to.

And now your agent has access to all these basic commands.

It has access to...

starting, stopping, forking databases, connecting the databases.

It also proxies another MCP server that we host where we have indexed the Postgres and Timescale and Tiger documentation.

And now we provide semantic search and text search on there.

So again, it's not just a CLI, it's not just a CLI MCP server, it's a CLI MCP server that actually makes your agent smarter.

I don't know.

I would say, I'm not sure if this is true, but it probably is.

This is probably the first AI-native CLI for Postgres.

It's not just like... I think other Postgres CLIs are just like API wrappers, but this is really thinking about bringing the CLI commands into the agent, but then also giving agents...