Accessing LinkedIn Data with Agent Reach: MCP Backend and Jina Reader Options

Agent Reach offers two distinct methods for accessing LinkedIn data: a full-featured MCP backend that delivers structured profile and company data, and a lightweight Jina Reader fallback for basic public page scraping.

Agent Reach treats every supported platform as a channel that implements a standardized contract defined in the base class. When accessing LinkedIn data with Agent Reach, the system automatically routes requests to the LinkedIn channel defined in agent_reach/channels/linkedin.py, which dynamically selects between available backends based on your local configuration.

LinkedIn Channel Architecture

The LinkedIn integration follows Agent Reach’s modular channel pattern, where each platform extends a generic Channel base class.

The Channel Contract

All channels inherit from the abstract Channel class in agent_reach/channels/base.py. This contract requires implementations of can_handle, read, search, and check methods. The LinkedIn channel is defined in agent_reach/channels/linkedin.py as:

class LinkedInChannel(Channel):
    name = "linkedin"
    description = "LinkedIn 职业社交"
    backends = ["linkedin-scraper-mcp", "Jina Reader"]
    tier = 2

The can_handle method automatically detects LinkedIn URLs by checking if the host contains linkedin.com, ensuring that any LinkedIn profile, company page, or post URL routes to this channel.

Backend Options for LinkedIn Access

Agent Reach provides two mutually exclusive backends for LinkedIn data retrieval, selected automatically based on your environment.

Option 1: Full MCP Backend (linkedin-scraper-mcp)

The linkedin-scraper-mcp backend delivers structured data including full profile details, company information, and job search capabilities. This requires:

1. The linkedin-scraper-mcp package installed
2. The mcporter command-line tool configured with a LinkedIn MCP server endpoint

To configure this backend:

pip install linkedin-scraper-mcp
mcporter config add linkedin http://localhost:3000/mcp

When properly configured, the channel communicates with the MCP server via mcporter to fetch rich, structured data rather than raw HTML.

Option 2: Jina Reader Fallback

If mcporter is missing or the LinkedIn MCP server is not configured, Agent Reach falls back to Jina Reader. This backend requires no additional installation and operates by scraping the public HTML of LinkedIn profiles or posts. While it provides basic content access, it lacks the structured data extraction and search capabilities available through the MCP backend.

Backend Selection Logic

The check method in agent_reach/channels/linkedin.py determines which backend is available by probing the local environment through agent_reach/probe.py.

If the probe detects that mcporter is missing, the channel returns a status of "off" along with configuration instructions:

if probe.status == "missing":
    return "off", (
        "基本内容可通过 Jina Reader 读取。完整功能需要：\n"
        "  pip install linkedin-scraper-mcp\n"
        "  mcporter config add linkedin http://localhost:3000/mcp\n"
        "  详见 https://github.com/stickerdaniel/linkedin-mcp-server"
    )

If mcporter is present but lacks a LinkedIn configuration, the channel similarly falls back to Jina Reader while prompting the user to add the MCP configuration. Only when mcporter reports a valid LinkedIn configuration does the channel activate the full MCP backend.

Implementation Examples

Command-Line Usage

After installing the package, use the agent-reach CLI to fetch LinkedIn data:

# Basic read using Jina Reader fallback (no setup required)

agent-reach read "https://www.linkedin.com/in/username"

# Full feature read after MCP configuration (structured data)

pip install linkedin-scraper-mcp
mcporter config add linkedin http://localhost:3000/mcp
agent-reach read "https://www.linkedin.com/in/username"

Programmatic Access

Use the AgentReach class from agent_reach/core.py to access LinkedIn data in Python:

from agent_reach.core import AgentReach

ar = AgentReach()

# Automatically detects LinkedIn URLs and selects appropriate backend

profile = ar.read("https://www.linkedin.com/in/elon-musk")
print(profile)  # Structured dict if MCP configured; raw HTML otherwise

# Access channel-specific search when MCP is active

if ar.channel("linkedin").active_backend == "linkedin-scraper-mcp":
    jobs = ar.channel("linkedin").search("software engineer")
    print(jobs)

Verifying Backend Status

Inspect which backend is currently active:

from agent_reach.channels.linkedin import LinkedInChannel

ch = LinkedInChannel()
status, hint = ch.check()
print(f"Status: {status}")          # "ok", "off", or "error"

print(f"Hint: {hint}")              # Installation/configuration advice

print(f"Active backend: {ch.active_backend}")  # "linkedin-scraper-mcp" or None

Summary

• Agent Reach implements LinkedIn support as a channel in agent_reach/channels/linkedin.py that extends the base Channel class.
• Two backends are available: the linkedin-scraper-mcp backend for structured data and full search capabilities, and Jina Reader for basic public page scraping.
• Automatic fallback occurs when mcporter is unavailable or unconfigured, ensuring basic functionality without setup.
• Configuration requires installing linkedin-scraper-mcp and running mcporter config add linkedin <URL> to enable full features.
• The routing engine in agent_reach/core.py automatically directs LinkedIn URLs to the appropriate channel based on URL host detection.

Frequently Asked Questions

What is the difference between the MCP backend and Jina Reader for LinkedIn?

The linkedin-scraper-mcp backend provides structured data extraction, including profile metadata, company details, and job search functionality, but requires installing the linkedin-scraper-mcp package and configuring an MCP server endpoint through mcporter. Jina Reader requires no setup and scrapes public LinkedIn pages as raw HTML, offering basic content access without structured data or search capabilities.

How do I configure the LinkedIn MCP server in Agent Reach?

Install the Python package linkedin-scraper-mcp, ensure mcporter is available in your environment, then run mcporter config add linkedin http://localhost:3000/mcp (adjusting the URL to your MCP server endpoint). The channel automatically detects this configuration on the next operation and switches from Jina Reader to the full MCP backend.

Can Agent Reach scrape LinkedIn without authentication?

The Jina Reader fallback can access public LinkedIn profiles and posts without authentication, as it reads publicly available HTML. However, the linkedin-scraper-mcp backend typically requires valid LinkedIn credentials configured within the MCP server itself to access detailed or restricted data.

Which file handles LinkedIn URL detection in Agent Reach?

URL detection is implemented in agent_reach/channels/linkedin.py within the LinkedInChannel class. The can_handle method inspects the URL host to identify strings containing linkedin.com, while the central routing logic in agent_reach/core.py coordinates channel selection across all supported platforms.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}