mcpField
P
Piloterr

Piloterr

Remote
piloterr.comBrowser Automation0Updated 1w ago

About Piloterr

Piloterr MCP Server connects MCP clients to Piloterr’s web scraping API, which returns structured data from more than 300 websites. Its compact tool catalog lets agents discover endpoint parameters before making API calls.

Key features

  1. 01Search the endpoint catalog
  2. 02Inspect endpoint parameters
  3. 03Call scraping API endpoints
  4. 04Check API usage and credits
  5. 05Return JSON, inline images, and embedded files

Use cases

  1. 01Collect structured data from supported websites
  2. 02Find the right endpoint before a scraping request
  3. 03Check remaining credits while using the API

MCP support

Exposes four tools to search endpoints, inspect parameters, call the Piloterr API, and view usage. It supports stdio and Streamable HTTP, with hosted or locally run deployment options.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.piloterr.com/
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.piloterr.com/Auth required
Packages
npm@piloterr/mcp0.1.0

Tools

Details

From the project README

Piloterr MCP Server

Official Model Context Protocol server for the Piloterr web scraping API.

Scrape 300+ websites (Amazon, LinkedIn, Google, Zillow, Crunchbase…) as structured JSON with one API.

It lets Claude, Cursor, VS Code, Windsurf and any MCP client call the API as tools. Runs over stdio (local) or Streamable HTTP (self-hosted).

Requirements

  • Node.js 20 or newer
  • a Piloterr API key — sign up, then copy it from the dashboard

Hosted server (recommended)

Piloterr runs this server for you at https://mcp.piloterr.com/ (Streamable HTTP). Send your API key in the x-api-key header; nothing to install.

claude mcp add --transport http piloterr https://mcp.piloterr.com/ --header "x-api-key: YOUR_API_KEY"
{
  "mcpServers": {
    "piloterr": {
      "url": "https://mcp.piloterr.com/",
      "headers": {
        "x-api-key": "YOUR_API_KEY"
      }
    }
  }
}

The hosted server and this package expose the same API; run the package locally when you want stdio, your own network egress, or to self-host it.

Run it locally

Claude Code
claude mcp add piloterr --env PILOTERR_API_KEY=YOUR_API_KEY -- npx -y @piloterr/mcp
Claude Desktop, Cursor, Windsurf and other clients

Add the server to the client's MCP configuration (claude_desktop_config.json, .cursor/mcp.json…):

{
  "mcpServers": {
    "piloterr": {
      "command": "npx",
      "args": ["-y", "@piloterr/mcp"],
      "env": {
        "PILOTERR_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}
VS Code
{
  "servers": {
    "piloterr": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@piloterr/mcp"],
      "env": {
        "PILOTERR_API_KEY": "${input:piloterr-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "piloterr-api-key",
      "description": "Piloterr API key",
      "password": true
    }
  ]
}
Claude Desktop extension

Download the .mcpb bundle from the releases page and open it; Claude Desktop asks for your API key.

Docker
docker build -t piloterr-mcp .
docker run -i --rm -e PILOTERR_API_KEY=YOUR_API_KEY piloterr-mcp

Tools

Piloterr has 391 endpoints, more than a client should load as separate tools. The server exposes a small catalog instead: the model searches it, reads an endpoint's parameters, then calls it.

ToolDescription
search_endpointsSearch the 391 Piloterr endpoints.
get_endpointDescribe the parameters of one endpoint.
call_endpointCall one Piloterr endpoint and return the result.
usageShow API usage and remaining credits.

Every tool that calls the API consumes credits. JSON results are returned as text; images are returned inline and other files (PDF…) as embedded resources, up to 4 MB.

Streamable HTTP

npx @piloterr/mcp --http --port 3000

The endpoint is POST /mcp (stateless, JSON responses). Each client sends its own key in the x-api-key header (or Authorization: Bearer <key>); the server never uses a key of its own. It binds to 127.0.0.1 by default and rejects browser origins unless you allow them — put it behind TLS before exposing it.

createHttpHandler() is exported for Fetch-compatible runtimes (Cloudflare Workers, Deno, Bun):

import { createHttpHandler } from "@piloterr/mcp";

export default { fetch: createHttpHandler({ allowedOrigins: [] }) };

Security

  • The API key is read from PILOTERR_API_KEY (stdio) or the request headers (HTTP) and removed from error messages.
  • Content fetched from websites is untrusted: the server instructions tell the model to treat it as data, not instructions.
  • See SECURITY.md to report a vulnerability.

Development

npm install
npm test
npm run build
npx @modelcontextprotocol/inspector node dist/stdio.js

Built on the SDK

The server uses the official Node.js SDK (@piloterr/sdk).

All Piloterr SDKs

SDKPackageInstall
Node.js@piloterr/sdknpm install @piloterr/sdk
Pythonpiloterrpip install piloterr
Gopiloterr-gogo get github.com/piloterr/piloterr-go
.NETPiloterrdotnet add package Piloterr
Rubypiloterrgem install piloterr
PHPpiloterr/sdkcomposer require piloterr/sdk
Javapiloterr-javabuild from source, see its README
CLI@piloterr/clinpm install -g @piloterr/cli
MCP server@piloterr/mcpnpx -y @piloterr/mcp

License

MIT — see LICENSE.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.