ClickRuntime for Any MCP client
A remote MCP server for webhook handlers and scheduled jobs
Give your own agent somewhere to put work that has to happen when an event arrives or keeps happening on a schedule: webhook handlers, monitors and scheduled jobs with run history and alerts. Standard MCP sign-in, no API keys and no client-specific setup.
About 2 minutes to connect. Free plan, no credit card.
Setup · about 2 minutes
Connect ClickRuntime to Any MCP client
Add a remote server in your client with this URL. Choose streamable HTTP if asked; do not add an Authorization header.
https://clickruntime.com/api/mcpStart the connection. The client receives a 401 and discovers sign-in through the protected-resource metadata, then registers itself (client ID metadata document or dynamic registration).
Sign in to ClickRuntime in the browser window the client opens, choose a workspace and approve.
Ask for an automation. The assistant turns it on and tests it, asking for your permission at each step.
Try it
A first automation to ask your MCP client for
Create a ClickRuntime automation: every hour, fetch this RSS feed and email me new items about pricing.
- A draft is savedYour client calls ClickRuntime and saves a draft. A draft does nothing on its own.
- You connect what it needsSlack, Google or an API key are connected once in the ClickRuntime application. Keys never go into the chat.
- You stay in controlYou allow each action in your assistant's permission prompt. Before a live run it tells you what starts it and every service it will contact. Every run is logged.
- It runs on its ownIt keeps running on ClickRuntime's servers with your MCP client closed, and tells you when something fails.
What people do with it
Automations people set up from Any MCP client
Watch a competitor's pricing page
Checks a pricing page every hour and posts a short summary to Slack only when something changes.
Log Stripe payments to Google Sheets
Every successful Stripe payment is added as a new row in a Google Sheet within seconds.
Triage new GitHub issues
Each new issue gets an AI summary and suggested label, posted to your team's Slack channel.
Weekly revenue summary from Stripe
Every Friday at 17:00 you get an email with the week's revenue, new customers and cancellations.
Check SSL certificates before they expire
Every Monday, your domains' certificates are checked and you get an email if any expire within 14 days.
Daily digest of new app reviews
Every morning, new reviews from your app's RSS feed are grouped by theme and emailed to you.
More things to ask Any MCP client
What can ClickRuntime do for me?
Create a ClickRuntime automation: every hour, fetch this RSS feed and email me items that mention 'pricing'.
Create a ClickRuntime automation: give me a trigger link that logs every POST body to a Google Sheet.
Apps
Apps your Any MCP client automations can use
- Slack
- Google Calendar
- Shopify
- Notion
- Telegram
- Asana
- Dropbox
- Calendly
- WordPress
- QuickBooks
- Bitbucket
- Evernote
- Square
- Wix
- Mailgun
- Sentry
- MySQL
- Firebase
- Cloudflare
- Spotify
- Miro
- Substack
- Product Hunt
- Etsy
- Wise
- Gusto
- RSS feeds
- Google Sheets
- Stripe
- Typeform
- Airtable
- Jira
- Mailchimp
- Discord
- Zendesk
- Google Docs
- Figma
- Box
- WooCommerce
- Squarespace
- Brevo
- Datadog
- MongoDB
- Vercel
- X
- YouTube
- Google Analytics
- Confluence
- Ghost
- Mastodon
- TikTok
- eBay
- Coinbase
- Okta
- Gmail
- GitHub
- HubSpot
- Google Drive
- Trello
- Zoom
- Linear
- Intercom
- Xero
- GitLab
- Todoist
- PayPal
- BigCommerce
- Webflow
- PagerDuty
- PostgreSQL
- Supabase
- Netlify
- Google Ads
- Bitly
- Medium
- Bluesky
- Twitch
- Revolut
- Zoho
- Auth0
Your control
What you control in Any MCP client
your MCP client can build, deploy, run, test and change an automation, and keeps fixing it until a run succeeds. You allow each action in Any MCP client's own permission prompt, and before a live run it tells you what it will send or change outside ClickRuntime. Keys are added only by you in the ClickRuntime dashboard, you can pause any automation at any time, and every run is logged.
Deleting needs one more step: in Any MCP client you confirm through a one-time link that opens ClickRuntime in your browser.
After it's live
Checking on and changing automations from Any MCP client
Check status
Ask whether an automation ran, when it runs next and how its recent runs went. your MCP client lists your automations with their state: live, paused or needing setup.
Ask your MCP client“Which of my ClickRuntime automations failed in the last 24 hours?”
Find out why a run failed
your MCP client reads the run's error and log lines, explains them in plain words and proposes a fix. You also get an email when a run fails.
Ask your MCP client“Show me the logs from the last failed run and fix the script.”
Change what it does
Move the time, add a recipient or change the logic. your MCP client applies the new version, tests it and tells you what changed. Every version is kept.
Ask your MCP client“Make the health check time out after 10 seconds instead of 30.”
Pause and resume
Pausing takes effect immediately, and you can pause from the ClickRuntime dashboard too. Events sent while paused are kept.
Ask your MCP client“Pause every automation that calls the staging API.”
Run it now
Trigger a one-off run to test a change or catch up after an outage. The schedule stays as it is, and the run counts toward your monthly runs.
Ask your MCP client“Run the scraper once now and show me the output.”
Clean up
Find automations you no longer need and delete them. Deleting removes the automation, its runs and its trigger link, so you confirm it first.
Ask your MCP client“List automations that haven't succeeded this month and delete the old test ones.”
Help
Any MCP client: troubleshooting and questions
Still stuck? See troubleshooting or contact support.
Discovery endpoints
Testing with MCP Inspector
What does my client need to support?
Why does my client show an Unverified tag on the approval page?
My client cannot open a browser. Can I use an API key?
Related pages
Keep exploring