ViralBrain

ViralBrain is not a Zero Human bridge. You bind the vendor's own server, the MCP server ViralBrain hosts, straight from Tools in the portal, signed in with your own ViralBrain account. Nothing of Zero Human's runs in between.

Not yet confirmed. Zero Human has not yet bound ViralBrain's server and recorded its tool names, its limits and its sign-in, or whether it covers X (formerly Twitter). Until it has, this page names no tools and does not claim that ViralBrain's sign-in works as a binding. This page changes once it is confirmed; there is no date for that yet. If your sign-in does not work in the meantime, write to [email protected].

What a member can do

With ViralBrain bound, a member can call the tools ViralBrain's server offers for LinkedIn posts. ViralBrain's own page says its MCP server is for LinkedIn only, and reads no analytics, comments or messages. Which tools it has, and what each does, is ViralBrain's to say, in its own documentation.

Each task names the ViralBrain tools it may call. viralbrain on a task means every tool ViralBrain's server offers; a single tool is named after the prefix, viralbrain.<tool>, as the server names it. A tool the task does not name is refused, whatever the binding allows. If ViralBrain's server does not answer when a run starts, the run carries on rather than failing, and its log on the run page records that the tool was not offered (tool.not_offered).

Who connects it

A ViralBrain binding acts as the ViralBrain account whose sign-in it holds. Everything it drafts or schedules is that account's, and reaches only what that account can.

A binding can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one above: task, then role, then member, then team, then enterprise. A binding on anything but a task also reaches the chat of every member it covers.

Bind ViralBrain on the task that calls it, as you connect Postmark on the task that sends. ViralBrain can schedule and publish posts as your account, and a binding on a member, team, role or the enterprise lets every chat it reaches do that without the task's skill, inputs or checks. A task's own binding never reaches chat. Bind it higher only when you want members to use it in chat too.

What waits for you

In a run, nothing on ViralBrain waits for you unless the task declares a gate on it. To see each post before it is scheduled or published, gate the tools that schedule or publish, or leave them off the task. See Gates and tool scopes.

Setup

Bind ViralBrain's server

1. In the portal, on Tools, choose Add tool. Layer: Task, and Bind on: the task that calls ViralBrain (see Who connects it for when to choose another layer).
2. Kind: MCP. Tool type: viralbrain.
3. MCP server URL: the server address ViralBrain gives for its hosted MCP server, in its own documentation.
4. Auth: the sign-in ViralBrain's documentation gives for that server. For a key, choose Bearer token / PAT, paste it, and set Header and Scheme to what ViralBrain asks for. For OAuth, choose OAuth and Connect with OAuth.
5. Name the tools on the task, viralbrain for all of them or each by name.
6. Check it. Run a task that saves one draft and publishes nothing. The run page shows the call and what ViralBrain returned.

To disconnect ViralBrain, delete the binding on Tools in the portal. A run of a task that names a ViralBrain tool then stops until one is bound again. To take the access back at the source too, revoke the key or the sign-in in your ViralBrain account.

Limits and cost

ViralBrain's limits are its own, and so is what its plans include: they are on your own ViralBrain account. Binding it has no Zero Human charge of its own. Its calls happen inside runs, and your plan counts those runs as it counts any other.

Troubleshooting

All of these show on the run page: a run that stops says why at the top, and Show log opens its full record. The words in code are what the page shows, so you can search this page for them.