MCP Resources Reference
Resources provide read-only access to your webhook data. Each resource has a unique URI and returns structured data in a consistent format.Resource URIs
All resources follow the pattern:webhook://[type]/[identifier]
| URI | Description |
|---|---|
webhook://events/recent | Last 100 webhook events |
webhook://requests/recent | Last 100 webhook requests |
webhook://webhooks/list | All configured webhooks |
webhook://events/recent
Returns the most recent webhook events across all your webhooks.Response Schema
Event Status Values
| Status | Description |
|---|---|
success | Event processed successfully |
failed | Event processing failed |
pending | Event queued for processing |
Provider Values
| Provider | Description |
|---|---|
stripe | Stripe payment webhooks |
github | GitHub repository events |
clerk | Clerk authentication events |
custom | Custom webhook providers |
webhook://requests/recent
Returns the most recent webhook HTTP requests made by your webhooks.Response Schema
Request Status Values
| Status | Description |
|---|---|
success | Request completed with 2xx status |
failed | Request failed with 4xx/5xx status |
timeout | Request timed out |
Common Status Codes
| Code | Description |
|---|---|
| 200 | OK - Request successful |
| 201 | Created - Resource created |
| 400 | Bad Request - Invalid payload |
| 401 | Unauthorized - Invalid signature |
| 404 | Not Found - Endpoint not found |
| 500 | Internal Server Error |
| 502 | Bad Gateway |
| 503 | Service Unavailable |
| 504 | Gateway Timeout |
webhook://webhooks/list
Returns all configured webhooks in your organization.Response Schema
Webhook Fields
Unique identifier for the webhook
Human-readable name
Optional description of the webhook’s purpose
The webhook provider (stripe, github, clerk, custom)
The Unhook URL to configure with the provider
Your endpoint that receives the webhooks
Whether the webhook is currently active
Webhook-specific configuration settings
Basic statistics about webhook performance
Data Limits
Resources are designed to provide quick access to recent data:- Events: Limited to 100 most recent events
- Requests: Limited to 100 most recent requests
- Webhooks: No limit (typically < 50 per organization)
Common Patterns
Checking Recent Failures
To quickly identify recent issues:- Read
webhook://events/recent - Filter events with
status: "failed" - Use event IDs to search for related requests
Monitoring Webhook Health
To assess webhook performance:- Read
webhook://webhooks/list - Check the
statsfield for each webhook - Identify webhooks with high failure rates
Debugging Specific Events
To investigate a particular event:- Read
webhook://events/recent - Find the event by ID or characteristics
- Note the
webhookIdandeventId - Use tools to analyze the event details
Error Responses
If a resource cannot be accessed, the response will include an error:Common Error Codes
| Code | Description |
|---|---|
NOT_FOUND | Resource does not exist |
PERMISSION_DENIED | No access to resource |
INTERNAL_ERROR | Server error occurred |
Best Practices
- Cache resource data - Resources update in real-time, but caching for 30-60 seconds is acceptable
- Use metadata - Check
hasMoreto know if older data exists - Combine with tools - Resources show recent data; use tools for historical analysis
- Monitor regularly - Set up periodic checks of webhook health
- Handle errors gracefully - Always check for error responses
Next Steps
- See Tools Reference for querying and analyzing data
- Check Integration Examples for usage patterns
- Review MCP Overview for protocol details