Give your agent a reliable clock.
Cronbolt is a remote MCP server for scheduling HTTP requests. A compatible agent can create, run, pause, resume, and inspect jobs without a browser session or a custom integration.
One endpoint, browser sign-in
https://api.cronbolt.com/mcpCronbolt opens in your browser so you can log in, choose a project, and approve access.
Stateless by default
MCP 2026-07-28 removes the HTTP session and initialization handshake. Each request can reach any healthy API replica.
Scoped to one project
Browser authorization issues an MCP-only token for the project you choose. It cannot read another project, account details, or billing.
The full schedule loop
Create recurring and one-time work, control job state, queue a run, and inspect redacted attempt history through typed tools.
What changed in MCP 2026-07-28
No handshake or session
Protocol version and client capabilities travel with every request. The former session ID and GET stream are gone.
Discovery before work
The newserver/discovermethod advertises supported versions and capabilities.
Hardened OAuth
Authorization uses discovery, PKCE, exact resource binding, and issuer validation. Access and refresh tokens stay separate from your Cronbolt login.
Routable and cacheable
Standard method and tool-name headers help gateways route calls, while deterministic lists and cache hints reduce repeat discovery work.
Connect in three steps
- 1. Add the MCP URLChoose Streamable HTTP and use the endpoint shown above.
- 2. Log in in your browserYour client opens Cronbolt through the standard OAuth flow.
- 3. Choose a projectApprove one project. Disconnect the client later from Settings.