CDNPulse Logo CDNPulse
CDNPulse
Get started
Get started

Using CDNPulse with AI Agents

CDNPulse exposes a fully documented REST API, an MCP server, and Agent Skills — so AI coding assistants can set up CDN monitoring and query analytics on your behalf.

Quick start: copy prompt for AI

The fastest way to get started with an AI assistant is to use the following prompt:

Help me set up CDN performance monitoring using CDNPulse (https://cdnpulse.io).

First read these skill guides:
- Setup: https://cdnpulse.io/.well-known/agent-skills/cdnpulse-setup/SKILL.md
- Analytics: https://cdnpulse.io/.well-known/agent-skills/cdnpulse-analytics/SKILL.md

Then help me: (1) sign up, (2) create an application for my website, (3) add the monitoring script, and (4) interpret the CDN performance analytics.

MCP server

CDNPulse exposes an MCP (Model Context Protocol) server at:

https://api.cdnpulse.io/mcp

This lets AI agents in Cursor, Claude Desktop, VS Code, and other MCP-capable clients call CDNPulse API operations directly as tools — no copy-pasting required.

Available tools

ToolDescription
get_all_appsList all your monitored applications
create_appRegister a new application
get_app_by_nameGet details of one application
update_appUpdate application settings
delete_appRemove an application
get_analytics_summaryAggregate metrics (TTFB, latency percentiles, error rate)
get_analytics_regionsPerformance breakdown by region
get_analytics_citiesPerformance breakdown by city
get_analytics_timeseriesHourly latency time series
get_analytics_dataFull analytics in one call
get_public_analytics_dataAnalytics for public apps (no auth)
get_public_analytics_timeseriesTime series for public apps (no auth)

Authentication

CDNPulse’s sign-in flow requires checking your email for a verification code, so it can’t be automated end-to-end. Obtain a Bearer token once via the REST API, then configure your MCP client to send it:

Step 1 — get a token (run once, e.g. with curl):

# 1. Request a code
curl -s -X POST https://api.cdnpulse.io/auth/signin \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]"}'

# 2. Check your inbox, then verify
curl -s -X POST https://api.cdnpulse.io/auth/verify \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]", "code": "123456"}'
# → {"access_token": "eyJ...", "token_type": "bearer"}

Step 2 — configure your MCP client:

{
  "mcpServers": {
    "cdnpulse": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://api.cdnpulse.io/mcp",
        "--header",
        "Authorization:Bearer ${CDNPULSE_TOKEN}"
      ],
      "env": {
        "CDNPULSE_TOKEN": "eyJ..."
      }
    }
  }
}
{
  "mcp": {
    "servers": {
      "cdnpulse": {
        "type": "http",
        "url": "https://api.cdnpulse.io/mcp",
        "headers": {
          "Authorization": "Bearer eyJ..."
        }
      }
    }
  }
}

Agent Skills

CDNPulse publishes Agent Skills — structured instruction files that AI agents can fetch to understand exactly how to use the API:

SkillURLDescription
cdnpulse-setup/cdnpulse-setup/SKILL.mdSign up, create an app, add the script
cdnpulse-analytics/cdnpulse-analytics/SKILL.mdQuery CDN performance metrics

The discovery index is at /.well-known/agent-skills/index.json (Agent Skills Discovery RFC v0.2.0).

REST API & OpenAPI spec

The full API is described in an OpenAPI 3.1 spec:

https://cdnpulse.io/openapi.yaml

You can paste this URL into any AI assistant or API client (Postman, Bruno, Scalar) to get a complete, interactive description of every endpoint.

OAuth Protected Resource metadata

For agents that support RFC 9728, CDNPulse publishes protected resource metadata at:

https://cdnpulse.io/.well-known/oauth-protected-resource

This tells agents the authorization server, supported scopes, and where to find the API spec.

Prev
Quickstart
Next
Metrics Reference