Integration guide

Give your n8n AI agent Google search and live data

By Khairul Muhtadin, n8n Ambassador

In n8n, connect your AI Agent to 1ToolRing with the MCP Client Tool node: set Endpoint to https://mcp.1toolring.com/mcp, Server Transport to HTTP Streamable, and Authentication to Bearer Auth with a 1ToolRing API key. The agent gets four tools (discover_tools, inspect_tool, run_tool, get_tool_run) and can fetch live Google results, keyword volume, Google Maps places, Amazon products and exchange rates, paying per call from a prepaid balance. For a fixed workflow with no agent, call the REST API from an HTTP Request node instead.

Set up the MCP Client Tool node

  1. Create an API key on the Keys page of the 1ToolRing console. It is shown once, so copy it now.
  2. Add an AI Agent node with a chat model, then add an MCP Client Tool node to its Tool connector.
  3. In the MCP Client Tool node, set Endpoint to the server URL:
    https://mcp.1toolring.com/mcp
  4. Set Server Transport to HTTP Streamable.
  5. Set Authentication to Bearer Auth, create a new credential and paste your API key as the token.
  6. Leave Tools to Include on All. The server lists exactly four tools.
  7. Open the chat, send the first prompt below and watch the agent call discover_tools, inspect_tool and run_tool.

Without an agent: the HTTP Request node

When the workflow always runs the same tool (say, a daily rank check for a list of keywords), skip the agent and call the REST API at https://api.1toolring.com directly. Find the tool id once, with discover_tools in a chat or with this call:

curl -X POST https://api.1toolring.com/api/v1/tools/discover \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"google search results for a keyword","limit":3}'

Configure the HTTP Request node

Method POST, URL https://api.1toolring.com/api/v1/tools/run. For Authentication choose Generic Credential Type, then Bearer Auth, with the same API key. Send a JSON body like this one, where {{ $json.keyword }} comes from the previous node:

{
  "tool": "dataforseo/serp/google-organic",
  "input": {
    "body": {
      "keyword": "{{ $json.keyword }}",
      "language_code": "id"
    }
  }
}

Slow runs and cost

A run that finishes in time answers 200 with the result in data.output and the charge in data.cost ({"usd", "idr"}). A slow tool answers 202 with a run_id: add a Wait node, then a GET request to the URL below, which is free, until status is completed or failed.

The X-ToolRing-Cost-USD and X-ToolRing-Cost-IDR response headers hold the exact charge if you want to log it. Read the input fields for any tool with POST /api/v1/tools/inspect; it is free too.

https://api.1toolring.com/api/v1/tools/runs/{{ $json.data.run_id }}

First prompt to try

Send this in the AI Agent chat. The agent should look up a tool, tell you the price, and then run it.

Use 1toolring to get the top Google results for "standing desk" in the United States. Tell me which tool you will use and its price before you run it, then list the top 10 URLs with their rank.

What the calls cost

A few tools your agent is likely to pick. Discovering and inspecting tools is free; only a successful run is charged. How pricing works.

Prices as of 5 Nov 2026; the live price is always shown before a run.
JobTool idPriceBilled
Live Google organic results, SERP features parseddataforseo/serp/google-organic$0.0026 (Rp48)per call (one page of 10 results)
Google search, every results-page element as JSONserpapi/google/search$0.0195 (Rp354)per successful search
Google Ads search volume, CPC and competitiondataforseo/keywords/google-ads-search-volume$0.117 (Rp2.122)per call (up to 1,000 keywords)
Google Maps places, or one place in fullserpapi/google/maps$0.0195 (Rp354)per successful search
Amazon search with price, rating and badgesdataforseo/amazon/products$0.0043 (Rp78)per call (one page of 48 results)
Daily exchange rates from a base currency1toolring/fx/latest$0.0003 (Rp5)per call

Troubleshooting

The node shows an SSE Endpoint field, or the transport is Server Sent Events
That is an older version of the MCP Client Tool node. 1ToolRing speaks Streamable HTTP, so add a fresh MCP Client Tool node (or update n8n) and choose HTTP Streamable.
"Authentication required" or 401 from 1toolring
The call arrived without a valid key. Check that Authentication is Bearer Auth and the credential holds the full key. The MCP server accepts the key only as Authorization: Bearer.
400 VALIDATION_ERROR from the run
The body does not match the tool's input. Read its input_schema with inspect and send only the parts it declares (body, queryParams or pathParams).
Tools answer 403 EARLY_ACCESS_PENDING
1ToolRing is in early access and new accounts are approved in batches. Sign-in works before approval, but tools, keys and top-ups stay locked until the approval email arrives. Nothing is charged for these calls.
A run fails with 402 INSUFFICIENT_BALANCE
The balance can't cover the price of that call. The error carries your balance, the amount needed and a top-up link. Top up any amount on the Billing page: from Rp10.000 by bank virtual account or Alfamart/Indomaret, or from $1 by card. The refused call costs nothing.
A tool answers 403 TOOL_BLOCKED
That tool is not offered on 1ToolRing, and nothing was charged. People or contact data, email finding, social media data and web scraping are not in the catalog. Ask your agent to pick another tool with discover_tools.

Questions

Can I use the MCP OAuth2 option in the node?
The node lists it. This guide uses an API key because a key can be created per workflow, given a budget and revoked from the console without touching other agents.
Do I need a separate account with each data provider?
No. You hold one 1ToolRing key and one prepaid balance, and that is the only account you need.

Related

Tool pages

Other guides

Steps checked against n8n docs: MCP Client Tool node (checked 2026-11-05).