[{"data":1,"prerenderedAt":36},["ShallowReactive",2],{"$f3p6xs28je2swq":3},{"href":4,"title":5,"description":6,"kind":7,"mark":8,"planned":9,"contributors":10,"provenance":8,"express":9,"html":11,"headings":12},"\u002Fdocs\u002Ftools\u002Fviralbrain","ViralBrain","LinkedIn posts, through ViralBrain's own hosted MCP server, on your own ViralBrain account.","integrates",null,false,[],"\u003Cp>ViralBrain is not a Zero Human bridge. You bind the vendor's own server, the MCP server ViralBrain hosts, straight\nfrom \u003Cstrong>Tools\u003C\u002Fstrong> in the portal, signed in with your own ViralBrain account. Nothing of Zero Human's runs in between.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Not yet confirmed.\u003C\u002Fstrong> Zero Human has not yet bound ViralBrain's server and recorded its tool names, its limits and\nits sign-in, or whether it covers X (formerly Twitter). Until it has, this page names no tools and does not claim\nthat ViralBrain's sign-in works as a binding. This page changes once it is confirmed; there is no date for that yet.\nIf your sign-in does not work in the meantime, write to \u003Ca href=\"mailto:hello@zerohuman.com\">hello@zerohuman.com\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"what-a-member-can-do\">What a member can do\u003C\u002Fh2>\n\u003Cp>With ViralBrain bound, a member can call the tools ViralBrain's server offers for LinkedIn posts. ViralBrain's own\npage says its MCP server is for LinkedIn only, and reads no analytics, comments or messages. Which tools it has, and\nwhat each does, is ViralBrain's to say, in its own documentation.\u003C\u002Fp>\n\u003Cp>Each task names the ViralBrain tools it may call. \u003Ccode>viralbrain\u003C\u002Fcode> on a task means every tool ViralBrain's server\noffers; a single tool is named after the prefix, \u003Ccode>viralbrain.<tool>\u003C\u002Fcode>, as the server names it. A tool the task does\nnot name is refused, whatever the binding allows. If ViralBrain's server does not answer when a run starts, the run\ncarries on rather than failing, and its log on the run page records that the tool was not offered\n(\u003Ccode>tool.not_offered\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Ch2 id=\"who-connects-it\">Who connects it\u003C\u002Fh2>\n\u003Cp>A ViralBrain binding acts as \u003Cstrong>the ViralBrain account whose sign-in it holds\u003C\u002Fstrong>. Everything it drafts or schedules is\nthat account's, and reaches only what that account can.\u003C\u002Fp>\n\u003Cp>A binding can sit on the enterprise, a team, a member, a role or a task, and the one further down replaces the one\nabove: task, then role, then member, then team, then enterprise. A binding on anything but a task also reaches the\n\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat\">chat\u003C\u002Fa> of every member it covers.\u003C\u002Fp>\n\u003Cp>Bind ViralBrain \u003Cstrong>on the task that calls it\u003C\u002Fstrong>, as you connect Postmark on the task that sends. ViralBrain can\nschedule and publish posts as your account, and a binding on a member, team, role or the enterprise lets every chat\nit reaches do that without the task's skill, inputs or checks. A task's own binding never reaches chat. Bind it\nhigher only when you want members to use it in chat too.\u003C\u002Fp>\n\u003Ch2 id=\"what-waits-for-you\">What waits for you\u003C\u002Fh2>\n\u003Cp>In a run, nothing on ViralBrain waits for you unless the task declares a gate on it. To see each post before it is\nscheduled or published, gate the tools that schedule or publish, or leave them off the task. See\n\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"setup\">Setup\u003C\u002Fh2>\n\u003Ch3 id=\"bind-viralbrains-server\">Bind ViralBrain's server\u003C\u002Fh3>\n\u003Col>\n\u003Cli>In the portal, on \u003Cstrong>Tools\u003C\u002Fstrong>, choose \u003Cstrong>Add tool\u003C\u002Fstrong>. \u003Cstrong>Layer:\u003C\u002Fstrong> Task, and \u003Cstrong>Bind on:\u003C\u002Fstrong> the task that calls\nViralBrain (see \u003Cstrong>Who connects it\u003C\u002Fstrong> for when to choose another layer).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Kind:\u003C\u002Fstrong> MCP. \u003Cstrong>Tool type:\u003C\u002Fstrong> \u003Ccode>viralbrain\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>MCP server URL:\u003C\u002Fstrong> the server address ViralBrain gives for its hosted MCP server, in its own documentation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Auth:\u003C\u002Fstrong> the sign-in ViralBrain's documentation gives for that server. For a key, choose \u003Cstrong>Bearer token \u002F PAT\u003C\u002Fstrong>,\npaste it, and set \u003Cstrong>Header\u003C\u002Fstrong> and \u003Cstrong>Scheme\u003C\u002Fstrong> to what ViralBrain asks for. For OAuth, choose OAuth and\n\u003Cstrong>Connect with OAuth\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Name the tools on the task, \u003Ccode>viralbrain\u003C\u002Fcode> for all of them or each by name.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Check it.\u003C\u002Fstrong> Run a task that saves one draft and publishes nothing. The run page shows the call and what\nViralBrain returned.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>To disconnect ViralBrain, delete the binding on \u003Cstrong>Tools\u003C\u002Fstrong> in the portal. A run of a task that names a ViralBrain tool\nthen stops until one is bound again. To take the access back at the source too, revoke the key or the sign-in in\nyour ViralBrain account.\u003C\u002Fp>\n\u003Ch2 id=\"limits-and-cost\">Limits and cost\u003C\u002Fh2>\n\u003Cp>ViralBrain's limits are its own, and so is what its plans include: they are on your own ViralBrain account. Binding\nit has no Zero Human charge of its own. Its calls happen inside runs, and your plan counts those runs as it counts\nany other.\u003C\u002Fp>\n\u003Ch2 id=\"troubleshooting\">Troubleshooting\u003C\u002Fh2>\n\u003Cp>All of these show on the run page: a run that stops says why at the top, and \u003Cstrong>Show log\u003C\u002Fstrong> opens its full record.\nThe words in code are what the page shows, so you can search this page for them.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>What you see\u003C\u002Fth>\n\u003Cth>Why\u003C\u002Fth>\n\u003Cth>What to do\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>The run stops and says no ViralBrain binding reaches it (\u003Ccode>tool_not_bound:viralbrain\u003C\u002Fcode>)\u003C\u002Ftd>\n\u003Ctd>No ViralBrain binding reaches this run\u003C\u002Ftd>\n\u003Ctd>Bind it on this task, or at a layer the run reaches: its member or the member's roles, the member's teams, or the enterprise\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>The run carries on without a ViralBrain tool, and its log says the tool was not offered (\u003Ccode>tool.not_offered\u003C\u002Fcode>)\u003C\u002Ftd>\n\u003Ctd>ViralBrain's server did not answer when the run started, or offers no tool by that name\u003C\u002Ftd>\n\u003Ctd>Check the server address and the tool's name in ViralBrain's documentation, then run it again\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Every ViralBrain call fails with a sign-in (auth) error\u003C\u002Ftd>\n\u003Ctd>The sign-in in the binding is not one ViralBrain's server accepts\u003C\u002Ftd>\n\u003Ctd>Edit the binding and enter the sign-in again, as ViralBrain's documentation gives it\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n",[13,17,20,23,26,30,33],{"id":14,"text":15,"level":16,"planned":9},"what-a-member-can-do","What a member can do",2,{"id":18,"text":19,"level":16,"planned":9},"who-connects-it","Who connects it",{"id":21,"text":22,"level":16,"planned":9},"what-waits-for-you","What waits for you",{"id":24,"text":25,"level":16,"planned":9},"setup","Setup",{"id":27,"text":28,"level":29,"planned":9},"bind-viralbrains-server","Bind ViralBrain's server",3,{"id":31,"text":32,"level":16,"planned":9},"limits-and-cost","Limits and cost",{"id":34,"text":35,"level":16,"planned":9},"troubleshooting","Troubleshooting",1793379253263]