DataForSEO

Integrates

Search results, keywords, backlinks and on-page audits, through DataForSEO's own hosted MCP server, on your own DataForSEO account.

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

Not yet confirmed. Zero Human has not yet bound DataForSEO's server and recorded its tool names and its sign-in. Until it has, this page names no tools and no prices, and does not claim that DataForSEO'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 DataForSEO bound, a member can call the tools DataForSEO's server offers for its own data: search engine results pages (SERP, what a search shows for a query), keywords, backlinks and on-page audits. Which tools those are, and what each returns, is DataForSEO's to say, in its own MCP documentation.

Each task names the DataForSEO tools it may call. dataforseo on a task means every tool DataForSEO's server offers; a single tool is named after the prefix, dataforseo.<tool>, as the server names it. A tool the task does not name is refused, whatever the binding allows. If DataForSEO'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 DataForSEO binding acts as the DataForSEO account whose sign-in it holds. Every call is made on that account, and DataForSEO bills each call it charges for to that account.

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 DataForSEO on the task that calls it, as you connect Postmark on the task that sends. DataForSEO charges for its calls, and a binding on a member, team, role or the enterprise lets every chat it reaches make them 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 DataForSEO waits for you unless the task declares a gate on it. DataForSEO charges for its calls, so gate the tools you want to approve first, or leave them off the task. See Gates and tool scopes.

Setup

Bind DataForSEO's server

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

To disconnect DataForSEO, delete the binding on Tools in the portal. A run of a task that names a DataForSEO 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 DataForSEO account.

Limits and cost

DataForSEO's limits are its own, and so are its prices: it bills its calls to your own DataForSEO 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.

What you see Why What to do
The run stops and says no DataForSEO binding reaches it (tool_not_bound:dataforseo) No DataForSEO binding reaches this run 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
The run carries on without a DataForSEO tool, and its log says the tool was not offered (tool.not_offered) DataForSEO's server did not answer when the run started, or offers no tool by that name Check the server address and the tool's name in DataForSEO's documentation, then run it again
Every DataForSEO call fails with a sign-in (auth) error The sign-in in the binding is not one DataForSEO's server accepts Edit the binding and enter the sign-in again, as DataForSEO's documentation gives it