MCP · Model Context Protocol

Give coding agents real website evidence.

HeronSignal MCP lets tools like Cursor use monitoring context while helping developers investigate and fix performance or frontend issues.

Request early access
Works with Cursor, Claude Desktop, and any MCP-compatible client
Read-only by default, and HeronSignal never writes to your codebase
Live data: errors, latency, deploy state, alarm events
Workspace-scoped, agents only see the context they need
How it works

Designed around the agent workflow.

HeronSignal MCP gives agents production evidence without exposing raw telemetry. Tokens are read-only by default; write scopes are narrow, explicit opt-ins.

scoped

Workspace-scoped context

MCP tokens are scoped to one workspace so coding agents only see the monitoring context they need.

read-only

Read tools

Agents can read AI analysis, page performance, frontend errors and logs, session journeys, traffic summaries, funnel results with conversion trends, health status, alarms, and per-issue trends to verify a fix worked.

opt-in

Narrow write scopes, never code

Optional per-token scopes let an agent create funnels or metrics and triage issues (resolve, ignore, reopen), shared with your team's Logger. No scope updates your repository or production code; fixes stay in the workflow you control.

paginated

No raw event dumps

HeronSignal returns summaries and paginated details instead of overwhelming agents with huge telemetry payloads.

Better fixes

Agents can connect code changes to real user pain, such as slow pages, broken clicks, failed APIs, or JavaScript errors.

Setup

Up and running in four steps.

One install on your site, one token in your editor. No infrastructure to maintain.

01
Install HeronSignal on your site

Add one script tag to your HTML. HeronSignal begins capturing visitor telemetry, errors, and performance data.

02
Generate an MCP token

From your workspace settings, create an MCP token scoped to one workspace: read-only by default, with optional write scopes you choose.

03
Add to your editor config

Paste the server block into your Cursor, Claude Desktop, or compatible MCP client config file.

04
Agent reads production context while you work

Ask your agent to investigate a slow page, a spike in errors, or a post-deploy regression. It reads the live data automatically.

Editor configcursor / claude
~/.cursor/mcp.json
{
"mcpServers": {
"heronsignal": {
"command": "npx",
"args": ["@heronsignal/mcp"],
"env": {
"HERONSIGNAL_TOKEN": "mcp_••••••••"
}
}
}
}
Connected · read-only
Example prompts

What you can ask your agent.

U
What broke after today's deploy?
U
Which pages have the slowest load times for mobile visitors?
U
Are there any JavaScript errors affecting the checkout flow?
U
What's the current status of the health checks?
U
Which alarm fired most recently and what triggered it?
U
What should I fix first based on real visitor data?

Give your coding agent the full picture.

Install HeronSignal, generate an MCP token, and your agent gains live access to performance, errors, sessions, funnels, health, and alarms.

Request early access