Testing the Amplitude <> Claude Connector

Today I tested the Amplitude ↔ Claude Connector for the first time. For those unfamiliar with Claude Connectors, they are just MCPs under the hood, but are showcased in a nice way on the Connectors page in Claude.

For some context, I work for a B2B SaaS startup and we use Amplitude for product analytics. As an IC product manager on a small team, I don’t have as much time as I’d like to learn how to use a full-featured product like Amplitude. Their UI confuses me, there are way too many modules in the sidebar, and we were forced into using them after they acquired June.so, which worked much better for our use case. So all in all, I have not spent much time in Amplitude since we migrated over.

But the Connector intrigued me, and I decided to try it out. It took me less than a minute to set up (click “Connect” and authenticate via my account), and I was able to chat with Claude and ask it what data I had available and what I should analyze.

It’s been hard to wow me lately with AI tools. With new models coming out every month and the capabilities getting better, some things just aren’t that impressive. But this really was, especially for my use case.

I ask Claude a question. It queries my Amplitude data, creates an Amplitude chart that I can import back into Amplitude’s custom report builder and save to run again later. And then of course does more analysis.

This is a HUGE plus for Amplitude. I also asked it to help me audit the tracked events, and we found a few key actions that we need to add tracking for.

Overall - if you would have asked me yesterday if I recommended Amplitude, I would’ve said no. But today, I’m whole-heartedly saying yes, if you use the Connector, because it makes it so ridiculously easy to get the insights you need, just by asking.