# Tapline [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://tapline.sh/docs/mcp  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tapline

## Description
Structured JSON from YouTube, Airbnb, TikTok, Instagram, Facebook, LinkedIn, Zillow, Google Maps and more. Hosted remote MCP with OAuth sign-in; four read-only tools.

## Claude Desktop Quick Installation
No generated config for this server: it installs through its own setup steps.

The project's own setup steps (from https://tapline.sh/docs/mcp), copied verbatim. Run them in order; they are not an mcpServers config.

1. Add to Claude Code:

```sh
claude mcp add --transport http tapline https://api.tapline.sh/mcp
```

2. Add to Codex:

```sh
codex mcp add tapline --url https://api.tapline.sh/mcp
```

3. Sign in:

```sh
codex mcp login tapline
```

## Documentation

## What Tapline does

Tapline provides structured JSON from a range of public-facing platforms and services, including YouTube, Airbnb, TikTok, Instagram, Facebook, LinkedIn, Zillow, and Google Maps. It is intended for AI agents that need to retrieve or extract information from these sources in a consistent machine-readable format.

The server exposes four tools, all of which are read-only. That makes Tapline suitable for workflows such as gathering search results, collecting listing or profile information, and passing extracted records into later agent steps. Because the available operations do not modify source accounts or content, it can be used where retrieval is the primary requirement.

## How it works

Tapline runs as a hosted remote MCP service rather than a local process. An MCP-compatible client connects to the hosted endpoint, and OAuth sign-in provides access. Tool calls return structured JSON for supported sources, allowing an agent to inspect and use the results without handling each platform through a separate integration.

The endpoint clients connect to is:

`https://api.tapline.sh/mcp`

## Setup and configuration

Configure the MCP client to use the remote endpoint above, then complete Tapline’s OAuth sign-in flow. There is no local package or runtime setup involved in using the hosted service. Client configuration details vary by MCP application, but the required connection target is the hosted URL.

After authentication, the client can discover and call Tapline’s available read-only tools. The service is accessed remotely, so network access to the endpoint is required.

## Tools and capabilities

Tapline offers four read-only tools for retrieving structured data. The supported source categories include:

- YouTube
- Airbnb
- TikTok
- Instagram
- Facebook
- LinkedIn
- Zillow
- Google Maps
- Additional supported sources

Results are returned as JSON, which makes them suitable for agent analysis, filtering, summarization, and downstream processing. The service is focused on data retrieval and extraction rather than actions that change content, listings, profiles, or other records.

## Limitations and notes

Tapline’s tools are read-only, so it should not be selected for workflows that need to publish, edit, delete, message, book, or otherwise mutate data on connected platforms. The service depends on OAuth authentication and a reachable hosted endpoint. Platform coverage extends beyond the named services, but the exact set of additional sources and the division of functionality across the four tools should be checked in the client’s discovered tool list.

_Full upstream README: https://allmcps.com/mcp/tapline/readme_

