From "add analytics" to first events in one request

Open your project in Cursor, Claude Code, or Codex and ask your agent to add Nexly. It picks the right SDK for your codebase, finds your existing app or creates a new one, lets the app accept traffic from your site, mobile app, or server, installs tracking with your credentials, and waits until the first events arrive. When they do, the app is marked as set up in the dashboard, exactly as if you had finished the setup wizard yourself.

The agent does not need instructions from you. Nexly gives it a built-in onboarding guide, so it knows the steps, what to check, and what to ask before changing anything. The new app onboarding also offers this path: copy the server address or open the setup guide, and the page moves on by itself once your agent has created the app.

Keep the app in shape afterwards

The same connection covers the work that usually comes after installation. Your agent can name and approve custom events and properties, build and edit funnels, exclude internal or test traffic with ingest filters, invite teammates as viewers or editors, and publish a public dashboard or report link when you ask for one.

Your role sets the limits

Every action runs with your own role in the app, so an agent can never do more than you can. Managing apps is a separate permission you approve on the authorization screen, and existing read-only connections stay read-only until you reconnect. Deleting an app, rotating keys, granting admin access, transferring ownership, and billing stay in the dashboard.

Connecting takes about two minutes, and the MCP setup guide covers each client. If you are new to MCP in Nexly, start with Ask Claude, Cursor, and Codex about your analytics.