MCPcat is now AgentCat

MCPcat is now AgentCat. Same team, same mission, new name.

Nothing about the product, how it works, our pricing, or our mission is changing. We're still helping teams build and improve their MCP servers, Claude Connectors, and ChatGPT Apps — understanding how agents use them, what they're trying to do, and where they get stuck. This is a name change, not a change in what we do.

Why the new name

The short version: more and more of the traffic hitting products today isn't human — it's agents. We're seeing this across all our customers and everyone we've talked to building the biggest software products today. We think the teams that win the next decade will be the ones that build a great experience for those agents, something we call Agent Experience (AX). We feel that AgentCat better encapsulates our vision of helping teams build products with incredible AX.

What's changing (and what isn't)

The name, our domain, and our SDK package names are changing. Your product experience isn't. Your project, data, dashboards, and history all stay exactly where they are.

The one thing developers will notice: our SDK is being renamed from mcpcat to agentcat.

Migrating your SDK

Here's the important part: nothing breaks, and there's no deadline.

• The old mcpcat package stays published and functional (permanently, not on a deprecation timer).
• api.mcpcat.io keeps accepting events
• Your data and history stay unified no matter which SDK sends them.
• New features only land in agentcat, so migrate whenever it suits you.

For instructions on how to update, see the detailed migration guides:

• TypeScript migration guide
• Python migration guide

What you need to do

Nothing today. Existing links, integrations, and SDK setups keep working. When you're ready for the latest features, follow the migration guide above.

Questions about the change? Open an issue on GitHub or email us at hi@agentcat.com.