What tools are on the hosted MCP at mcp.piloterr.com?

The full Piloterr OpenAPI library: website crawl/render engines plus LinkedIn, Amazon, Google, email, domain, and marketplace endpoints. Check https://mcp.piloterr.com/health for the current tool count. A custom MCP server is only needed if you want a smaller local subset.

Why doesn't https://mcp.piloterr.com/ open in my browser?

It is an MCP server over Streamable HTTP, not a web page. MCP clients send GET with Accept: text/event-stream (and other protocol headers) to complete the handshake. Use Cursor, Claude Code, Codex, Gemini CLI, ChatGPT Developer mode, or Hermes Agent, not a normal browser tab.

How do I authenticate the hosted server?

Create an API key in the Piloterr dashboard and pass it as the x-api-key header on every request. Cursor: headers in Settings or .mcp.json. Claude Code: --header with claude mcp add. Codex: http_headers in ~/.codex/config.toml. Gemini CLI: headers next to httpUrl. ChatGPT Developer mode: connector secret. Hermes Agent: headers.x-api-key in ~/.hermes/config.yaml.

Do I still need a custom server for LinkedIn or Amazon?

No for the full hosted surface: those library endpoints are already MCP tools on mcp.piloterr.com. Build a custom server only when you want a curated subset or stdio locally.

How do I check the hosted server is up?

Open https://mcp.piloterr.com/health in a browser, unlike the MCP endpoint, the health route is a plain HTTP check you can hit directly.

MCP & IDE agents

Call Piloterr from Cursor, Claude Code, Hermes Agent, 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.

Start free (+500 credits)View pricing

Hosted MCP at https://mcp.piloterr.com/, full library tools, no local process
Streamable HTTP, connect from Cursor, Claude Code, Codex, Gemini CLI, ChatGPT Developer mode, or Hermes Agent
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

Works with

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, Codex, Gemini CLI, ChatGPT Developer mode, or Hermes Agent.
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), Codex (~/.codex/config.toml), Gemini CLI (mcpServers httpUrl), ChatGPT Developer mode (remote MCP connector), Hermes Agent (~/.hermes/config.yaml).

Why MCP + Piloterr beats raw fetch in agents

Approach	DIY	Piloterr
Browser fetch tool	Blocked on protected sites	Managed anti-bot bypass
Copy-paste cURL	Manual, not composable	Typed MCP tools
HTML in context	Token-heavy, noisy	Compact JSON fields
Ops overhead	Proxies, headless Chrome	Hosted or single API key

Connect MCP in four steps

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
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.
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, Codex, Gemini CLI, ChatGPT Developer mode, or Hermes Agent).
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.
Hermes Agent + hosted MCP
Add mcp.piloterr.com under mcp_servers in ~/.hermes/config.yaml with x-api-key, then /reload-mcp for the full library.
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.

Browse API library

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

Hosted MCP, mcp.piloterr.com Server health check Website Crawler API Website Rendering API Model Context Protocol Cursor MCP docs Hermes Agent MCP docs

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

View all plans and credit modes →Estimate your monthly usage →

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

Start free (+500 credits)Talk to a data expert

Call Piloterr from Cursor, Claude Code, Hermes Agent, and MCP clients

Why connect MCP

Hosted MCP | full library

Not a web page

Custom MCP | optional subset

Production-grade bypass

What the hosted MCP covers

Full library tools

Website crawl and render

Always in sync with the API

Client compatibility

Why MCP + Piloterr beats raw fetch in agents

Connect MCP in four steps

Create an API key

Use the hosted server (recommended)

Configure your MCP client

Verify and test

Workflow recipes

Hosted: crawl from Cursor

Hosted: library toolbox

Claude Code + hosted MCP

Hermes Agent + hosted MCP

Custom subset when needed

Hosted vs custom MCP

Full Piloterr library from the IDE

Trimmed tool list or offline stdio

Scheduled production pipelines

No-code SaaS triggers