API, webhooks and MCP
Pro and Team plans. Create a key in Settings, API keys, then use it with the REST API, the MCP server, or both. A key acts as the person who made it, inside one workspace, and can never do more than that person can in the app.
REST API
- Base address https://mergescheduler.gentlesoni.online/api/v1, with an OpenAPI file at /api/v1/openapi.json.
- Access levels: read, schedule and admin.
- Schedule, reschedule, cancel and revert releases; list repos and pull requests; check whether a pull request is ready; add and change repos (admin).
- Times are ISO 8601 with a UTC offset. Idempotency-Key makes retries safe. Limits: 60 requests a minute and 2,000 a day per key.
Webhooks
- Signed HTTPS calls (Standard Webhooks) when a release is scheduled, cancelled, skipped, merged, deployed, fails its deploy, is reverted, or needs attention.
- Retries after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. Only https addresses; private networks are refused.
- Verification examples in Node and Python.
MCP server
- Address https://mergescheduler.gentlesoni.online/mcp, using the same keys, over streamable HTTP.
- Tools to list repos and pull requests, check a pull request, and schedule, move, cancel and revert releases.
- Setup examples for Claude Code and Cursor. Any MCP client that supports remote servers with a custom header works.