You want your Bolt app to snapshot account metrics every Monday, even when nobody has the project open. The clean split is: Bolt builds and publishes the server function, while Crontap owns the recurring HTTP call. Bolt's custom connector can manage that schedule from chat because its official setup explicitly documents HTTP transport, MCP OAuth, and tools that can read, create, or edit data. You need a Crontap account, a published Bolt project with a database, and permission to add connectors.
Before you start
- The Bolt connector is a build-time chat capability. It is not bundled into the published app.
- Keep a shared function secret in Bolt Database or Supabase Secrets and in the Crontap schedule UI.
- Verified against Bolt MCP connectors, server functions, and database logs on 2026-09-15.
Build and publish the server function
Step 1
Create a metrics snapshot function
Ask Bolt for a server function called snapshot-account-metrics. It should
accept POST, verify X-Snapshot-Key against the SNAPSHOT_KEY secret,
calculate the previous week's account totals, and upsert one row keyed by the
week's start date. Upsert makes retries safe.
Create a server function named snapshot-account-metrics. Accept POST only, require X-Snapshot-Key to match the SNAPSHOT_KEY database secret, calculate the previous calendar week's active-account totals, and upsert one snapshot row keyed by week_start so retries cannot duplicate data.Step 2
Store the secret and publish
Click the database icon, open Secrets, create SNAPSHOT_KEY, and publish the
app. Open the database icon again, choose Server Functions, and find the
function. Call its deployed HTTPS URL with curl: expect 401 without the
header, then expect the week and snapshot count with X-Snapshot-Key. Use
View Logs to inspect the request.
Connect Crontap to Bolt chat
Step 3
Add the custom MCP connector
From the Bolt homepage chatbox, choose the plus icon, Connectors, then Manage
connectors. Select Custom MCP server. Name it Crontap, set the URL to
https://mcp.crontap.com/mcp, choose HTTP as the transport, choose MCP OAuth,
and click Connect. Complete Crontap authorization.
- Crontap
- Connected
- Authentication
- OAuth 2.1
Review the discovered tools from the connector's Edit screen. Bolt enables all tools by default, and its tool selection applies across projects rather than per project. Disable destructive tools you do not need. Turn the Crontap connector on only for the current project.
Step 4
Preview and create the weekly request
Ask Bolt to preview Mondays at 06:15 in America/New_York. Then create a
POST schedule using the published function URL. Review the tool
confirmation. After creation, open the schedule in Crontap and add
X-Snapshot-Key directly in the UI.
Use Crontap MCP to preview Mondays at 06:15 in America/New_York. Show the three upcoming runs and do not create anything yet.Create a schedule named "weekly account snapshot" that POSTs to https://YOUR-APP.example/functions/v1/snapshot-account-metrics using the previewed cadence. Before calling the create tool, repeat the URL, method, timezone, and cadence for approval. Do not include request secrets.Step 5
Verify the same call in both products
Retrieve the new schedule by ID in Bolt chat. In Crontap, perform a test request after adding the header. Open Bolt's database logs, filter for Server Function, and confirm the matching invocation. Check that only one snapshot row exists for that week.
What a successful setup looks like
The Bolt connector should show Connected, and the project toggle should be on. The MCP create result should include one schedule ID and the next run. A follow-up read should match the endpoint, method, timezone, and cadence you approved.
Crontap history should show the test request's HTTP result and duration. Bolt's Server Function log proves its runtime received the request. The snapshot table proves the business operation completed. Run one more test to verify the upsert updates the same weekly row rather than creating a duplicate.
Where the recurring request runs
Bolt server functions are the right place for authenticated HTTP logic, and View Logs shows each invocation. Bolt's current user documentation does not give a procedure for creating a native recurring schedule.
If you deploy through a provider with a documented scheduler, that provider can run the job. Use Crontap when you want recurring calls to the published URL with separate request history and MCP management.
Troubleshooting
The custom connector will not connect
Use HTTP, not SSE, for Crontap and include the /mcp path. Choose MCP OAuth, then allow the browser sign-in. Workspace policy or permissions may prevent adding a connector.
Tools appear in settings but not the project
Open the plus menu in the project chat, choose Connectors, and enable Crontap for that project. Refresh the connection if Bolt has not re-discovered the tool list.
Bolt proposes a secret in the tool call
Reject the call. Create the schedule without endpoint credentials, then add the secret header in Crontap. The MCP transcript should contain the header name at most, never its value.
The function returns 404 or 401
For 404, verify that the copied URL belongs to the published server function rather than preview. For 401, compare the secret stored in Bolt with the value added in Crontap.
Two weekly rows appear
Make the function's database write an upsert with a unique week_start key. Manual tests, retries, and overlapping schedules can produce repeated calls.
Next steps
- Return to the Crontap MCP hub for resource and approval details.
- Compare the connector workflow in Lovable and the deployment choices in Replit.
- Read Schedule tasks in Bolt apps for additional endpoint patterns.
Ready to manage the recurring call? Free forever tier. No credit card. Create your Crontap account →
Verified against current official Bolt documentation on 2026-09-15. Sources: Bolt MCP connectors, Bolt server functions, Bolt secrets, and Bolt database logs.
FAQ
Bolt scheduling questions
- Can Bolt connect directly to Crontap MCP?
- Bolt documents custom MCP servers using HTTP or SSE and MCP OAuth. Choose HTTP, enter Crontap's MCP URL, and complete the sign-in flow.
- Does the MCP connector run inside the published Bolt app?
- No. The connector is available to Bolt while you build. The published server function receives normal scheduled HTTP requests from Crontap.
- Does Bolt have a documented native scheduler?
- Bolt's current user documentation does not provide a native schedule-creation procedure. This guide uses Crontap to call the published server function on a recurring schedule.
- Where should the server function secret live?
- Store it in Bolt Database or Supabase Secrets and in the Crontap schedule UI. Do not pass the value through Bolt chat or MCP tool arguments.