Install
$ agentstack add mcp-blocknextai-blocknext ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
BlockNext
BlockNext is a no-code platform for building and running AI-powered workflows. Design flows on a drag-and-drop canvas, connect AI models and third-party services, and let your automations run — no code required.
It is built for end users, not just developers: flows stay simple, readable and predictable by design.
Highlights
- Visual flow builder — compose workflows on an intuitive drag-and-drop canvas. Nodes take arrays in and return arrays out, so a node fed ten items runs ten times and emits ten results — batch work needs no loop construct. What is missing is deliberate: no
while/foron the canvas, no sub-workflows, no expression language to learn. - Describe it, don't configure it — give a node plain-language instructions and an LLM fills in its parameters at run time. Anything you set explicitly always wins over what the model infers. This one and flow generation are the only features that need a key of your own (Gemini); both are off by default. Everything else — the canvas, triggers, the MCP server, every integration node — works on a fresh install.
- Built-in MCP server — every integration node doubles as an MCP tool. Point Claude (or any MCP client) at your BlockNext server with an API key and use your connected services from chat.
- AI-powered nodes — LLMs and generative AI (text, image, audio, video) as first-class building blocks, alongside integrations for the tools you already use.
- Async done right — long-running AI jobs (video, music generation) are a single node. The node starts the job, polls the provider, and returns the finished result — no wait/check/loop scaffolding on your canvas.
- Featherweight self-hosting — Go services on distroless images (15–32 MB each). A fresh install runs 7 containers and no Redis, idling around 100 MB of RAM — PostgreSQL is nearly half of that. Runs comfortably on the smallest VPS.
- Scale when you need to, not before — the cache, realtime broker, leader election, concurrency semaphore and task runner all default to in-process providers. Point them at Redis when you run more than one instance; Compose starts a backing service only once something is configured to use it.
- Triggers — start flows manually, on a schedule, or from the outside via webhooks and API calls.
- Live execution view — watch every task and node progress in real time over WebSocket.
- Credentials management — encrypted at rest, OAuth tokens auto-refreshed, and only ever decrypted at execution time — flows never embed secrets.
Curious how it works under the hood? See the [architecture overview](ARCHITECTURE.md).
Getting started
make setup # creates .env with generated secrets
make docker-up # pulls the published images and starts the full stack
Docker and make are all you need — Go and Bun are only required for [development](.github/CONTRIBUTING.md).
The UI is served on http://localhost:4000. Run make help for every target.
One thing to know on a fresh install: EMAIL_SENDER_PROVIDER defaults to log, so every outbound mail is printed instead of sent. Signing up with a password does not wait for verification — you land in the app straight away — but magic-link sign-in and password reset need the link, and it is in make docker-logs. Point the sender at SMTP, Resend or SendGrid when you have credentials.
To build and run everything from source instead, see [CONTRIBUTING.md](.github/CONTRIBUTING.md) — the development workflow uses make local-docker-up.
Upgrading
Set BLOCKNEXT_VERSION in .env to the release you want (it defaults to latest), then:
make docker-pull
make docker-up
Migrations run in their own container before the services start, so schema changes are applied for you.
Community
- [Architecture overview](ARCHITECTURE.md)
- [Contributing guide](.github/CONTRIBUTING.md)
- [Code of Conduct](.github/CODEOFCONDUCT.md)
- [Security policy](.github/SECURITY.md) — please report vulnerabilities privately
License
BlockNext is licensed under the [Apache License 2.0](LICENSE).
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: blocknextai
- Source: blocknextai/blocknext
- License: Apache-2.0
- Homepage: https://platform.blocknext.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.