MCP Resources
Resources provide read-only data feeds that AI agents can access for context. Unlike tools (which perform actions), resources provide passive data.
Documentation Resources
Available without authentication.
statly://docs/llms.txt
Complete Statly documentation formatted for AI consumption.
statly://docs/llms.txtContains:
- SDK installation and configuration
- API reference
- Code examples for all languages
- Platform feature documentation
- Troubleshooting guides
This resource is automatically included when AI clients request context about Statly. It's the same content served at https://docs.statly.live/llms.txt.
statly://docs/api
REST API reference documentation.
statly://docs/apistatly://docs/sdk/javascript
JavaScript SDK documentation.
statly://docs/sdk/javascriptstatly://docs/sdk/python
Python SDK documentation.
statly://docs/sdk/pythonstatly://docs/sdk/go
Go SDK documentation.
statly://docs/sdk/goLive Data Resources
These resources require authentication and provide real-time data from your organization.
statly://org/monitors
Live data for all monitors in your organization.
statly://org/monitorsReturns:
{
"monitors": [
{
"id": "mon_abc123",
"name": "Production API",
"url": "https://api.example.com/health",
"status": "operational",
"uptime_24h": 99.98,
"last_check": "2024-01-15T12:00:00Z",
"response_time_ms": 145
}
],
"summary": {
"total": 10,
"operational": 9,
"degraded": 1,
"outage": 0
}
}statly://org/incidents
Active and recent incidents.
statly://org/incidentsReturns:
{
"active": [
{
"id": "inc_xyz789",
"title": "Elevated API Latency",
"status": "identified",
"severity": "minor",
"created_at": "2024-01-15T11:30:00Z",
"affected_monitors": ["mon_abc123"]
}
],
"recent": [
{
"id": "inc_def456",
"title": "Database Connection Issues",
"status": "resolved",
"resolved_at": "2024-01-14T22:15:00Z"
}
]
}statly://org/maintenance
Scheduled maintenance windows.
statly://org/maintenanceReturns:
{
"upcoming": [
{
"id": "maint_123",
"title": "Database Migration",
"start_time": "2024-01-20T02:00:00Z",
"end_time": "2024-01-20T04:00:00Z",
"affected_monitors": ["mon_db1", "mon_api"]
}
],
"in_progress": []
}statly://org/status
Current overall status summary.
statly://org/statusReturns:
{
"overall": "operational",
"components": {
"api": "operational",
"database": "operational",
"cdn": "degraded"
},
"active_incidents": 0,
"scheduled_maintenance": 1,
"uptime_30d": 99.95
}statly://org/subscribers
Subscriber statistics (privacy-preserving).
statly://org/subscribersReturns:
{
"total": 1250,
"verified": 1180,
"unverified": 70,
"by_preference": {
"incidents_only": 450,
"maintenance_only": 120,
"all_updates": 680
}
}For privacy, individual subscriber emails are not exposed through resources. Use the subscribers/list tool with appropriate permissions to access subscriber details.
Using Resources
Automatic Context
MCP clients often automatically fetch relevant resources when starting a session. For example, when you ask about Statly integration, your AI client may automatically fetch statly://docs/llms.txt.
Explicit Resource Requests
You can explicitly request resources by asking your AI:
"Load my monitors resource to see current status"
"Fetch the Statly SDK documentation resource"
Resource vs Tool
Use resources when you need to:
- Get current state/context
- Provide background information to the AI
- Reference documentation
Use tools when you need to:
- Perform an action (create, update, delete)
- Get specific filtered data
- Trigger operations (test integrations, send notifications)
Resource Freshness
| Resource | Update Frequency |
|---|---|
| Documentation | Updated on deployment |
| Monitors | Real-time (current state) |
| Incidents | Real-time (current state) |
| Maintenance | Real-time (current state) |
| Status | Real-time (current state) |
| Subscribers | Real-time (current counts) |
Live data resources always reflect the current state when fetched. There is no caching at the MCP server level.