add-tavily-tool

Installs Tavily Search and Extract as keyless remote MCP tools for NanoClaw agent groups.

30.7k|12.8k|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/nanocoai/nanoclaw --skill add-tavily-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-tavily-tool
Source: https://github.com/nanocoai/nanoclaw/tree/main/.claude/skills/add-tavily-tool
Command: npx skills add https://github.com/nanocoai/nanoclaw --skill add-tavily-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp-remote.

What problem does it solve?

NanoClaw agent groups on non-Claude providers lack built-in web search and URL extraction tools, and setting up a remote MCP server manually involves image rebuilds, per-group registration, and credential handling that is easy to get wrong.

Core Features & Use Cases

  • Keyless MCP registration: Installs the pinned mcp-remote bridge in the agent container image and registers Tavily's remote MCP server per group, exposing tavily_search and tavily_extract without an API key.
  • Dependency guard and verification: Copies a vitest manifest test into the host tree, rebuilds the image, and verifies the stored group configuration and a live search call.
  • Upgrade path for rate limits: Writes standing instructions into each group's instructions.prepend.md so the agent offers a OneCLI vault-based API key upgrade when the shared keyless allowance returns 429.
  • Use Case: An operator running NanoClaw agents on OpenCode or Codex wants web search; this skill registers Tavily for the selected groups, restarts them, and confirms a live search succeeds.

Quick Start

Ask the agent to add Tavily web search and URL extraction to your selected NanoClaw agent groups using the add-tavily-tool skill.

Frequently Asked Questions about add-tavily-tool

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add Tavily web search to NanoClaw agent groups?

Add the pinned mcp-remote entry to container/cli-tools.json, rebuild the image, then run ncl groups config add-mcp-server with the tavily name and keyless header for each group. Restart each group and verify with a live tavily_search call.

Does Tavily MCP require an API key for NanoClaw agents?

No, the registration uses the X-Tavily-Access-Mode:keyless header, which enables Tavily's IP-based free allowance shared across groups on the host. When that allowance is exhausted, a paid key can be stored in the OneCLI vault without the agent ever seeing it.

Which Tavily tools are exposed through the MCP server?

Only tavily_search and tavily_extract are exposed. The registration passes --ignore-tool flags for tavily_crawl, tavily_map, and tavily_research, so those tools never appear in the Tavily namespace.

Why do I get command not found: mcp-remote after registering Tavily?

The mcp-remote bridge is missing from the agent container image. Rebuild the image with ./container/build.sh after adding the manifest entry, then restart the affected group so it picks up the new binary.

What happens when the Tavily keyless allowance runs out?

Tavily returns HTTP 429 or monthly_cap_reached_bonus_eligible. If the Phase 5 upgrade block is installed, the agent offers a OneCLI dashboard deeplink where the user saves a free API key, then re-registers the server without the keyless header.