Blinkbox — an open-source automation platform (Zapier/n8n-style) exposed as an MCP server, so Cursor builds and runs your workflows

Showcase Built for Cursor
,
1

Hi all — I maintain Blinkbox, an open-source automation platform (triggers → nodes → actions, ~250 integrations with OAuth for Google/Slack/Notion/Airtable/GitHub/Microsoft, headless Chromium scraping, sandboxed JS). The whole platform is exposed as an MCP server, so Cursor’s agent can build, run and iterate on workflows instead of you dragging nodes.

Setup in Cursor (2 min)

  1. Sign up at https://blinkbox.net (free, no card) → dashboard → MCP tab → copy the URL and create a key.
  2. Cursor Settings → MCP → add a server: URL https://mcp.blinkbox.net/mcp, header Authorization: Bearer <your key> (Streamable HTTP).
  3. Download the SKILL.md from the same MCP tab and drop it in your rules/skills so the agent knows the node catalog and expression syntax — with it a working flow is ~4 tool calls instead of ~12 of guessing.

Tools exposed: list/create/update/run automations, activate/deactivate, list executions + read logs, node catalog + per-node config lookup, credentials. OAuth stays in the UI: the agent wires “Google Sheets”, you click Connect once.

A real run: I asked for “a daily 8am lead finder: query OpenStreetMap for dentists/vets/hairdressers in a city, keep only places with website + email + phone, dedupe against my Google Sheet, append the new ones.” It built a 16-node flow (cron → 3 HTTP → merge → qualify → sheet read → filter → condition → append). First draft ran green and wrote nothing (new URL() isn’t in the sandbox; wrong key after a merge node) — one follow-up message fixed both. Run 1: 3 leads, run 2: 0 (dedupe works). On a cron since.

Repo (self-hostable, Node 22 + Mongo + Redis): GitHub - blinkboxhq/Blinkbox: Open-source automation platform (Zapier/Make/n8n alternative) with a native MCP server — your AI builds and runs the workflows · GitHub

Rough edges: docs are thin, the free tier is small, and per-node output isn’t in the logs tool yet (fixing next — an all-green run that writes nothing is the failure mode). Would love to hear what breaks for Cursor users specifically.