Nimble

Search, extract, map and crawl the live web from your AI assistant.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Nimble connector does

The Nimble MCP server connects Nimble's web-data platform to Claude, ChatGPT and any MCP-compatible agent. It exposes 18 tools that search, extract, map and crawl live websites and run Nimble's Web Search Agents. Every fetch tool takes a free-form URL, so the real question is not what Nimble holds but where the connector can reach.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Nimble tools (18)

  • nimble_search
  • nimble_extract
  • nimble_extract_async
  • nimble_map
  • nimble_crawl_run
  • nimble_crawl_status
  • nimble_crawl_list
  • nimble_crawl_terminate
  • nimble_task_results
  • nimble_agents_list
  • nimble_agents_get
  • nimble_agents_run
  • nimble_agent_run_async
  • nimble_agents_status
  • nimble_agents_generate
  • nimble_agents_publish
  • nimble_agents_update_from_agent
  • nimble_agents_update_session

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The connector can reach any host not on the deny-list. There is no allowlist, and the reach includes state-changing HTTP methods, arbitrary headers and cookies. Gate it at the client if the agent takes untrusted input.
  • Roughly 78 domains are blocked across all Web APIs and the proxy service, so payment, streaming and gaming targets will simply fail.
  • Metering is per successful result, and a single instruction can consume thousands of units. On a Data Services plan, exceeding your credits bills as overage rather than stopping.
  • Credits expire monthly. They roll over within a billing cycle only.
  • Rate limit is 83 QPS (5,000 QPM) on the default drivers. Exceeding it returns HTTP 429.
  • Agent generation is capped at 100 per customer per day, across API, CLI, SDK and the Agent Builder skill.
  • No MCP page covers security. Nimble's untrusted-content warning and its SSRF discussion live on two SDK connector pages, not on the MCP server page the directory links to.
  • We could not read tool schemas. The endpoint is OAuth-gated and we did not authenticate, so there are no MCP safety annotations on this page — no readOnlyHint, no openWorldHint, no per-tool parameter list. Absence of annotations is not evidence that tools are read-only. The tool names come from Anthropic's directory; behaviour comes from Nimble's documentation and OpenAPI specification.
  • We could not establish whether the MCP tools expose the full REST parameter set, including method, headers, cookies and browser_actions. The REST API has them; whether the MCP layer narrows them is unverified in both directions.
  • We could not find a registered tool total. Nimble's llms.txt, changelog and pricing pages state no MCP tool count, so 18 is Anthropic's figure with nothing to corroborate it.

Frequently asked questions

Can the Nimble MCP server fetch any URL on the internet?

Yes, with one exception. Nimble's own API schema types the target of extract, map, crawl and media as a plain string with no allowlist, so the connector reaches whatever host the agent names. The only stated restriction is a published deny-list of roughly 78 domains — payment, streaming and gaming brands — that Nimble rejects across every Web API and its proxy service.

Does the Nimble connector only read pages, or can it change things?

It can change things on the sites it visits. Nimble's extract schema accepts an HTTP method of GET, POST, PUT, PATCH or DELETE with an arbitrary request body, and its browser-actions feature clicks and fills form fields — the vendor's own worked example submits a login form. Anthropic's directory nevertheless labels the whole connector Read, which understates that reach.

What does the Nimble MCP server charge for, and when?

It charges per successful result, not per call. Nimble's pricing page states twice that only successful requests are charged, and bills extraction at one dollar per thousand URLs, search at $1.10 to $5.00 per thousand inputs, and Web Search Agent runs at a flat $0.025 to $2.00 per task by effort level. A deep search adds a live-extraction surcharge on top.

What happens when Nimble credits run out mid-run?

The request fails outright with HTTP 402 Payment Required, so exhaustion is visible rather than silent. Nimble's rate-limit reference maps 402 to no budget, limit reached, trial expired or trial quota finished, and its error guide repeats that the code means credits are exhausted. On a paid Data Services plan, overage is billed at pay-as-you-go rates instead of blocking the call.

Does Nimble warn that scraped web pages can hijack an agent?

It does, but not where an MCP user would look. Nimble writes that returned content is untrusted web data, to be treated as data rather than instructions, on its LlamaIndex connector page, and it discusses giving up an SSRF guard twice on its Vercel eve page. The MCP server documentation page carries no security or trust section at all.

How many Nimble MCP tools are there, and does the vendor list them?

Anthropic's directory lists 18, and Nimble enumerates no complete set anywhere. Its Claude connectors page names five tools, its Google ADK page names five, and both call that a curated subset while pointing at an MCP reference page that describes six product areas rather than tools. Thirteen of the 18 listed names appear in no vendor document.

Which OAuth scopes does the Nimble MCP server ask for?

Four, and two of them are real application scopes: nimble:read and nimble:write, alongside openid and offline_access. Nimble's authorization server advertises exactly the same four, so there is no wider vocabulary being withheld from this resource. That read-and-write split is unusually candid — most connectors in this catalogue offer a single coarse grant or none at all.

Can I use the Nimble MCP server with an API key instead of OAuth?

Yes, and the two paths differ by client. Nimble's MCP documentation shows Cursor, Claude Code and Claude Desktop passing a bearer API key in an Authorization header, while its Claude connectors page routes claude.ai through OAuth with no key needed. The endpoint itself answers an anonymous request with an OAuth challenge, verified live.

Sources

More Data & Research connectors

  • Airfield Directory

    Look up airfields, landing fees, fuel prices, pilot reports and METAR/TAF from an AI agent.

  • Airtable

    Read, write and restructure Airtable bases from your AI assistant.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Nimble to work.

Connect Nimble once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio