Skip to main content
Piloterr
MCP logo

MCP & IDE agents

Call Piloterr from Cursor, Claude Code, and MCP clients

Connect to our hosted MCP at mcp.piloterr.com (Streamable HTTP) and get the full Piloterr library as tools, or run a custom MCP server if you need a local subset over stdio.

  • Hosted MCP at https://mcp.piloterr.com/, full library tools, no local process
  • Streamable HTTP, connect from Cursor, Claude Code, Gemini CLI, or ChatGPT Developer mode
  • LinkedIn, Amazon, Google News, website crawl/render, and the rest of the library
  • Same x-api-key header and credit pool as the REST API

At a glance

Hosted

mcp.piloterr.com

190+

library tools

HTTP

Streamable MCP

Custom

optional subset

Why connect MCP

  • Hosted MCP | full library

    https://mcp.piloterr.com/ speaks MCP over Streamable HTTP. Add it as a remote HTTP server with x-api-key, no local install. Every OpenAPI operation from the Piloterr library is registered as an MCP tool.

  • Not a web page

    Opening the URL in a browser tab will not work: only MCP clients send the required Accept headers to complete the handshake. Use Cursor, Claude Code, Gemini CLI, or ChatGPT Developer mode.

  • Custom MCP | optional subset

    Prefer a smaller surface or stdio locally? Run your own MCP server that wraps only the REST endpoints your team needs.

  • Production-grade bypass

    Tools call Piloterr server-side: WAF, CAPTCHA, and JS rendering are handled before JSON reaches the model.

What the hosted MCP covers

One remote endpoint, the full product surface.

  • Full library tools

    LinkedIn, Amazon, Google, company enrich, email, domain, and marketplace scrapers, each exposed as a typed MCP tool from the OpenAPI spec.

  • Website crawl and render

    Website Crawler, Website Rendering, WebUnlocker, screenshots, and related fetch engines for any URL your plan allows.

  • Always in sync with the API

    Tools are generated from the live OpenAPI document, so new library endpoints show up on the hosted MCP as the API grows.

  • Client compatibility

    Cursor (Settings → MCP, HTTP streamable), Claude Code (claude mcp add --transport http), Gemini CLI (mcpServers httpUrl), ChatGPT Developer mode (remote MCP connector).

Why MCP + Piloterr beats raw fetch in agents

ApproachDIYPiloterr
Browser fetch toolBlocked on protected sitesManaged anti-bot bypass
Copy-paste cURLManual, not composableTyped MCP tools
HTML in contextToken-heavy, noisyCompact JSON fields
Ops overheadProxies, headless ChromeHosted or single API key

Connect MCP in four steps

  1. Step 1

    Create an API key

    Sign up for Piloterr, open the dashboard, and create an API key. Send it as the x-api-key header on every MCP request.

    Create an API key
  2. Step 2

    Use the hosted server (recommended)

    Point your client at https://mcp.piloterr.com/ for the full library. Use a custom local server only if you need a trimmed tool list or stdio.

  3. Step 3

    Configure your MCP client

    Add an HTTP (streamable) server pointing to https://mcp.piloterr.com/ with x-api-key in headers (Cursor .mcp.json, Claude Code, Gemini CLI, or ChatGPT Developer mode).

  4. Step 4

    Verify and test

    Check https://mcp.piloterr.com/health for the tool count, then ask your agent to call any library tool (LinkedIn, Amazon, crawl, and more).

Workflow recipes

  • Hosted: crawl from Cursor

    Agent calls mcp.piloterr.com to fetch and render a competitor page while you write integration code.

  • Hosted: library toolbox

    Use LinkedIn, company enrich, SERP, and marketplace tools from the same remote MCP without a local process.

  • Claude Code + hosted MCP

    claude mcp add --transport http piloterr https://mcp.piloterr.com/ --header "x-api-key: …" for the full library in the terminal.

  • Custom subset when needed

    Keep hosted MCP for most work, and add a small local server only for a curated internal tool list.

Hosted vs custom MCP

  • Scenario

    Full Piloterr library from the IDE

    Recommendation: Hosted MCP (Streamable HTTP)

  • Scenario

    Trimmed tool list or offline stdio

    Recommendation: Custom MCP server (stdio)

  • Scenario

    Scheduled production pipelines

    Recommendation: n8n or SDK

  • Scenario

    No-code SaaS triggers

    Recommendation: Zapier or Make

Hosted config and optional custom server

Remote Streamable HTTP at mcp.piloterr.com for the full library, or a local stdio server for a custom subset.

JSON
{
  "mcpServers": {
    "piloterr": {
      "url": "https://mcp.piloterr.com/",
      "headers": {
        "x-api-key": "your-x-api-key"
      }
    }
  }
}

Transparent credit pricing

Pay only for successful requests. Start with +500 credits, then scale with plans from $49/mo.

Premium

$49/mo

18,000 credits

Premium+

$99/mo

40,000 credits

Startup

$249/mo

110,000 credits

Ready to get started?

Your web scraping API is one click away. Start with +500 credits, no infrastructure to set up, no proxies to manage, and no credit card required.

  • +500 credits
  • No credit card required
  • All endpoints included