MCP Server

FetchLayer runs a single Model Context Protocol server exposing all 34 live platforms as tools — no per-platform setup, no glue code.

Connection details

Server URL https://mcp.fetchlayer.dev

Transport streamable-http

Server card fetchlayer.dev/.well-known/mcp/server-card.json

Authentication

Use your FetchLayer API key as a Bearer token in the Authorization header — the same pattern as the REST API.

Bearer header (recommended)

Most MCP clients — including Claude Desktop and Cursor — let you set custom headers per server:

json

{
  "mcpServers": {
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev",
      "headers": {
        "Authorization": "Bearer ss-your-key"
      }
    }
  }
}

Or, calling the server directly over HTTP:

bash

curl -X POST https://mcp.fetchlayer.dev \
  -H "Authorization: Bearer ss-your-key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Inline path key (not recommended)

If your client's config has no headers field — just a URL — pass the key inline as a /k/<key> path prefix instead.

json

{
  "mcpServers": {
    "fetchlayer": {
      "url": "https://mcp.fetchlayer.dev/k/ss-your-key"
    }
  }
}

Prefer the Bearer header when you can

A key embedded in the URL can end up in logs, shell history, or proxy records. Only use the /k/ form when your client genuinely has no way to send a custom header.

Tip

Don't have a key yet? Sign up for a free API key — no credit card required.

Tools

Every endpoint is exposed as a tool named scrape_<platform>_<endpoint> — for example scrape_reddit_search. Call tools/list for the full, always-current list.

The number beside each platform is how many tools it contributes. Docs for each are one click away.

On this page