Your analytics, inside the tools you already use
Nexly now supports MCP, the open protocol that lets AI assistants such as Claude, Cursor, and Codex work with external services. Add Nexly as a connector, and your assistant can answer questions about your traffic right in the conversation: how visits changed over the last month, which pages drive the most signups, what last week's report says, or where a funnel loses momentum.
Claude tracing a traffic spike to its source with the Nexly MCP server
There is nothing to install and no keys to copy. Connecting a tool opens a familiar authorization screen where you approve access with your Nexly account, the same way you sign in with Google elsewhere. The whole setup takes about two minutes, and the MCP setup guide walks through Claude, Cursor, and Codex step by step. Other MCP clients that support OAuth, such as Grok, connect the same way.
Read-only by design
Before you approve a connection, the authorization screen shows exactly what the tool will be able to do: read analytics, reports, funnels, and property details available to your account. That is the entire surface. Connected tools can query your data, but they can never change settings, properties, or anything else in your account.
Connections use the OAuth standard, so no passwords or long-lived secrets ever reach the assistant, and access can be withdrawn at any moment.
Stay in control
Every tool you authorize appears in Settings → Connected apps, along with when it was connected and last used. Disconnect an app there and it loses access immediately; reconnecting later takes the same two minutes. The guide shows what that screen looks like.
Curious what assistants can actually query? Start with the Insights overview, see how Nexly tracks AI-referred traffic, or browse Features for the broader picture. And if you are also tracking mobile apps, the Flutter and Swift SDKs send app traffic to the same property your MCP tools can read.