v0.1.17 — final mcpcat release (renamed to agentcat)

MCPcat is now AgentCat 🐱 — same team, same product, new name.

This is the final release of the mcpcat package. It has been renamed to agentcat (npm install agentcat, starting fresh at v1.0.0). No functional or dependency changes — this release only adds the rename notice on every surface npm gives us:

• README callout linking the migration guide
• [DEPRECATED — mcpcat is now agentcat: npm install agentcat] package description
• A one-time notice line in ~/mcpcat.log when track() runs (never stdout/stderr — STDIO MCP safety)
• The npm registry entry is marked deprecated, so npm/pnpm/yarn print the notice at install time

Nothing you have deployed will break — ever. The mcpcat package, api.mcpcat.io, and MCPCAT_API_URL stay alive permanently. Migrate on your own schedule — new features land only in agentcat.

Migration guide: MIGRATION.md · PR: #46

agentcat v1.0.0 — MCPcat is now AgentCat 🐱

Same team, same product, same cats — new name. MCPcat is now AgentCat, and this SDK's first release under its own name is agentcat@1.0.0 on npm.

What's new

• 📦 npm package: mcpcat → agentcat (fresh start at v1.0.0)
• 🌐 Default endpoint: api.mcpcat.io → api.agentcat.com
• 🏷️ Public types: MCPCatOptions / MCPCatData / MCPCatIDPrefixes → AgentCatOptions / AgentCatData / AgentCatIDPrefixes
• ⚙️ Env vars: reads AGENTCAT_API_URL first; MCPCAT_API_URL still honored
• 📝 Local log: ~/mcpcat.log → ~/agentcat.log

Nothing you have deployed will break — ever

The mcpcat package stays published and functional, api.mcpcat.io keeps accepting events forever, and your project, data, and history stay unified regardless of which SDK reports. Migrate on your own schedule — new features land here.

Migrating

npm uninstall mcpcat && npm install agentcat

Then rename imports and types 1:1 — full steps (and a paste-into-your-coding-agent prompt) in MIGRATION.md.

v0.1.14

What's New

Event Tags & Properties

• New eventTags and eventProperties callbacks on track() options for attaching custom metadata to every auto-captured event
• Tags: indexed string key-value pairs (validated client-side, max 50 entries)
• Properties: flexible JSON metadata with no constraints
• Also available on publishCustomEvent() via the CustomEventData object

PostHog AI Observability Integration

• New enableAITracing option on PostHogExporterConfig
• Emits $ai_span events for tool calls alongside regular capture events
• Maps MCPCat sessions to $ai_session_id/$ai_trace_id and tool calls to $ai_span_id/$ai_span_name
• Customer tags can override any $ai_* default for custom trace/span grouping

Exporter Improvements

• All exporters include source: "mcpcat" for attribution
• Datadog: customer tags namespaced with mcpcat. prefix, key/value sanitization
• Sentry: customer properties in contexts.mcpcat (moved from deprecated extra), tags namespaced with mcpcat.
• OTLP: customer tags as mcpcat.tag.* span attributes
• PostHog: customer tags and properties spread directly as top-level event properties

Other

• $ now allowed in tag key names (for PostHog $ai_* overrides)
• Tags and properties exempt from redaction pipeline
• MCPCAT_SOURCE constant replaces hardcoded strings across all exporters

Full Changelog: v0.1.13...v0.1.14

v0.1.13

What's Changed

Features

• Add PostHog telemetry (#24)
• Add content sanitization for non-text MCP data types (#25)
• Add client-side event truncation (100KB max) (#27)

Bug Fixes

• Stop publishing error events for identify function failures (#21)

Maintenance

• Upgrade mcpcat-api to 0.1.7 (#23)

Full Changelog: v0.1.11...v0.1.13

v0.1.7

Changes

• Improved context parameter with detailed instructions (#8)

Installation

npm install mcpcat@0.1.7
# or for beta releases
npm install mcpcat@beta