[{"_1":2,"_3":-5,"_4":-5},"loaderData",{"_5":6,"_7":8,"_9":10},"actionData","errors","root",{"_119":120},"routes/modules.$creator.$moduleId",{"_14":15,"_16":17,"_18":19,"_20":21},"routes/modules.$creator.$moduleId.endpoints",{"_11":12,"_13":-5},"error","Module not found","tools","module",{"_20":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":26,"_36":37,"_38":-5,"_39":-5,"_40":41,"_42":43,"_44":45,"_46":47,"_48":47,"_49":50,"_51":52,"_53":54,"_55":-5,"_56":47,"_57":58,"_59":60,"_61":62,"_63":64,"_65":66,"_67":47,"_68":69,"_70":71,"_72":73,"_74":75,"_76":77,"_78":-5,"_79":-5,"_80":-5,"_81":47,"_82":-5,"_83":84,"_85":86,"_87":88,"_89":90,"_91":92,"_93":94},"apiUrl","https://odel.app/api","creator","noclickapp","moduleId","noclick","@noclickapp/noclick","displayName","NoClick","tagline","Build agents to automate any background task. Works with your ChatGPT/Claude subscription.","iconKey","https://www.noclick.com/icon-512.png","category","remote","status","published","visibility","public","metaDescription","deploymentType","external","workerName","bindingName","mcpConfig","{\"url\":\"https://api.noclick.io/mcp\",\"transport\":\"streamable-http\",\"authType\":\"none\"}","pricingModel","free","creatorUserId","system:external-import","createdAt",1788069131000,"updatedAt","sourceRegistry","official-mcp-registry","sourceUrl","https://registry.modelcontextprotocol.io/v0/servers?search=io.github.noclickapp%2Fnoclick","sourceVerified",true,"sourceMissingSince","importedAt","upstreamStars",1,"upstreamUpdatedAt",1788068375000,"detectedTransport","streamable-http","detectedAuthType","oauth","probeStatus","ok","lastProbedAt","githubRepoUrl","https://github.com/noclickapp/noclick","githubRepoFullName","noclickapp/noclick","releaseId","ext-noclickapp-noclick","version","1.0.0","descriptionMarkdown","

\n \n $\"NoClick\"$ \n \n

\n\n

\n Describe an agent. Watch it get built. Let it run.
\n Workflow automation with AI agents at the core — a visual canvas, ~160\n integrations, and coding agents that can actually use your tools.\n

\n\n

\n Website ·\n Docs ·\n Self-hosting ·\n Discord ·\n Contributing\n

\n\n

\n $\"npm\"$ \n $\"PyPI\"$ \n $\"Discord\"$ \n

\n\n

\n $\"Deploy$ \n $\"Deploy$ \n $\"Deploy$ \n

\n\n

\n \n $\"Typing$ \n \n

\n\n## Quick start\n\nTry NoClick with [npx](https://docs.npmjs.com/cli/v10/commands/npx) — requires\n[Node.js](https://nodejs.org) 18+ and [Docker](https://docs.docker.com/get-docker/):\n\n```bash\nnpx noclick\n```\n\nOr with one line of shell, no Node required:\n\n```bash\ncurl -fsSL https://noclick.com/install.sh | sh\n```\n\nOr by hand — the same thing, visibly:\n\n```bash\ngit clone https://github.com/noclickapp/noclick.git && cd noclick\n./scripts/noclick-setup.sh\ndocker compose up -d\n```\n\nEach installer path fetches the source, generates this instance's secrets —\nincluding the credential-encryption key, which is kept across re-runs — and\nstarts the stack with Docker Compose. Re-running updates in place. Releases are\ntags; pin the exact source the installer builds with `NOCLICK_REF=v0.2.2`. The\ninstaller deliberately builds that checkout locally. If you operate the Compose\nstack directly, `NOCLICK_VERSION=0.2.2 docker compose up -d` instead pins the\nreleased backend image; the frontend is still built for your public URLs. Every\ninstaller option is documented at the top of [`install.sh`](https://github.com/noclickapp/noclick/blob/main/install.sh).\n\nThen open the editor at [http://localhost:3000](http://localhost:3000).\n\n---\n\n## What is NoClick?\n\nNoClick lets you build automations on a visual canvas and run them on triggers —\nwebhooks, schedules, inbound email, or chat messages from Slack, WhatsApp and\nfriends. What makes it different is the agent layer: an AI agent node can drive\nreal coding harnesses (Claude Code, Codex, opencode, hermes, OpenClaw) and call\nyour connected integrations as tools, so an agent can read a Linear issue, work\nin a git repo, and post the result back to Slack.\n\nThis repository is the platform: the workflow engine, every integration node,\nthe React editor, the realtime collaboration layer, the AI workflow builder,\nand an MCP server. It's the same code that runs [noclick.com](https://noclick.com).\n\n

\n $\"The$ \n

\n\n## What you can build\n\n- **Automations on a canvas** — chain ~160 integrations (Slack, Gmail, Notion,\n Linear, HubSpot, Stripe, Postgres, Google Sheets, …) with branching,\n iteration, filters, and code nodes.\n- **Triggers** — webhooks, cron schedules, inbound email, and app events from\n Slack/Discord/HubSpot; channel-style agents that reply where they're spoken\n to, with as many triggers per workflow as you need.\n- **AI agents with real tools** — wire integration nodes into an agent's tool\n handle and it can call those operations directly. Agent nodes run either\n in-process (any OpenAI/Anthropic/OpenRouter-compatible model) or as a coding\n harness using your own installed CLI.\n- **Interfaces** — publish a form, dashboard, or chat over any workflow.\n- **Build with AI** — describe what you want and the builder assembles the\n workflow on the canvas. It's also exposed over MCP, so you can point Claude\n Code (or any MCP client) at your instance and have it build for you.\n\n## How it works\n\n1. **Describe it.** Type what you want into the builder — or point any MCP\n client at your instance and let your coding agent do the describing.\n2. **The builder assembles it.** Nodes appear on the canvas wired to real\n operations, asking only for what it genuinely needs: credentials, and the\n choices only you can make.\n3. **It runs on triggers.** A message arrives, a webhook fires, a schedule\n ticks — the workflow executes, agents call their tools, and results land\n where you told them to. Every run records its tool calls, timings, and the\n agent's response, so you can see exactly what happened.\n\n## Self-hosting\n\nThe installer above is the fast path. For a real deployment — your own Postgres,\nobject storage, OAuth apps for integrations, model providers, and the\nenvironment variables each side needs — read the\n**[self-hosting guide](https://github.com/noclickapp/noclick/blob/main/docs/self-hosting.md)**.\n\nThe deploy buttons above ask for nothing: Railway and Render create a Postgres\ndatabase next to the reviewed release image (DigitalOcean binds a managed\ncluster named `noclick-db` you create first), and the instance does the rest on\nfirst boot — it runs its own auth layer, prepares the database, and generates\nits own keys. Railway uses [`railway.template.json`](https://github.com/noclickapp/noclick/blob/main/railway.template.json),\nRender [`render.yaml`](https://github.com/noclickapp/noclick/blob/main/render.yaml), DigitalOcean\n[`.do/deploy.template.yaml`](https://github.com/noclickapp/noclick/blob/main/.do/deploy.template.yaml), and Fly\n[`fly.toml`](https://github.com/noclickapp/noclick/blob/main/fly.toml). See the\n**[hosted deployment guide](https://github.com/noclickapp/noclick/blob/main/docs/self-hosting.md#hosted-deployments)** for\nwhat each one provisions and where its secrets live.\n\nReleases are what you run: `main` moves with every upstream merge, tags are\ndeliberate cuts, and each tag publishes images to GHCR so the compose stack\npulls rather than builds. Pin with `NOCLICK_VERSION`.\n\n## Developing from source\n\nPrerequisites: Docker, the [Supabase CLI](https://supabase.com/docs/guides/cli),\nPython 3.12 (3.13 isn't supported yet — some pinned wheels don't build on it),\nNode.js 20 or newer, and pnpm 10.34.4 (or npm for running package scripts).\n\n```bash\npip install -r requirements.txt\nmake local\n```\n\nThat boots everything on your machine — a local Supabase (Postgres, auth,\nstorage), the backend, and the frontend — and prints a URL. Sign up with any\nemail; local auth confirms instantly. No cloud account, no API keys required to\nget to a running canvas.\n\n```bash\n# Backend\ncd backend && python server.py # or: uvicorn server:web_app\npytest # test suite\n\n# Frontend\ncd frontend && npm run dev\nnpm run typecheck && npm run build && npm test\n\n# Database migrations\ncd infra && supabase migration up --local\n```\n\n## Architecture\n\n| Path | What lives there |\n|---|---|\n| `backend/nodes/` | Every integration node — one module per service, self-describing config schemas |\n| `backend/wss/` | Socket.IO event layer: handlers, typed events, the workflow execution engine |\n| `backend/coder/workflow/` | The XML workflow DSL, graph state, and the AI builder |\n| `backend/mcp_server.py` | MCP server exposing workflow construction to any MCP client |\n| `backend/utils/` | Shared services: webhooks, credentials, storage, relay, cron |\n| `frontend/app/` | Remix + Vite app: ReactFlow canvas, config panels, interface builder |\n| `infra/supabase/` | Database migrations |\n| `sdk/` | The `noclick` TypeScript SDK for embedding published workflows |\n\nNode config UIs are generated from the backend's Pydantic models, so adding an\nintegration is mostly writing one Python module — the editor picks it up.\n\n## NoClick Cloud\n\n[noclick.com](https://noclick.com) is the hosted platform. It runs this engine\nplus managed infrastructure: retained agent runtimes so turns resume instantly,\nscaled webhook and cron delivery, additional hosted builder capabilities, and\nmanaged storage and email. Self-hosted and cloud share the same workflow\nformat, so workflows move between them unchanged.\n\n## Contributing\n\nIssues and pull requests are welcome. Adding an integration node is the easiest\nplace to start: copy the closest existing node in `backend/nodes/`, register it\nin `backend/nodes/core/registry.py`, and the config UI generates itself.\n\n**[CONTRIBUTING.md](https://github.com/noclickapp/noclick/blob/main/CONTRIBUTING.md)** covers the architecture you need to know\nand the conventions this codebase enforces. `AGENTS.md` / `CLAUDE.md` carry the\nsame guidance for coding agents, so pointing Claude Code or Codex at a checkout\ngets you working changes rather than plausible-looking ones.\n\nCome say hello in **[Discord](https://discord.com/invite/sHC2mrnss8)** — it's the\nfastest way to get a question answered.\n\n## License\n\n[Sustainable Use License 1.0](https://github.com/noclickapp/noclick/blob/main/LICENSE.md) — use and modify it for your own\ninternal business purposes, or for non-commercial and personal use. You may pass\nit on only free of charge and non-commercially. It is source-available rather\nthan open source: there is no time-based conversion to a permissive licence, and\ncommercial redistribution — including offering it as a hosted service — needs a\nseparate agreement. [LICENSE.md](https://github.com/noclickapp/noclick/blob/main/LICENSE.md) is the authority; this paragraph\nis a summary and not a term of it.\n","changelogMarkdown","videoKey","requiredSecretsJson","publishedAt","priceCents","trialDays",0,"upstream",{"_105":106,"_107":108,"_109":110,"_111":112,"_113":114,"_115":116},"requiredSecrets",[],"tags",[97,98,99,100,101,102,103,21,104],"assets",[],"stats",{"_95":84,"_96":84},"ratingAvg","reviewCount","agents","ai","aiagents","automation","integration-framework","integrations","ipaas","self-hosted","topics",[97,98,99,100,101,102,103,117,118,21,104],"license","NOASSERTION","language","Python","registryName","io.github.noclickapp/noclick","homepage","https://www.noclick.com/mcp","packages",[],"mcp","mcp-server","ENV",{"_121":122,"_123":124,"_125":126},"ENVIRONMENT","production","TURNSTILE_SITE_KEY","0x4AAAAAAB8-rEI2gNDf_QhU","SENTRY_DSN","https://45fd1229f78089d5c3ee78be128030e1@o4510583261757440.ingest.de.sentry.io/4510584253448272"]