Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.linkup.so/llms.txt

Use this file to discover all available pages before exploring further.

Developed by Anthropic, the Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to LLMs. It is particularly helpful when building agents and complex workflows on top of LLMs.
Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools.
-Anthropic
Learn more about the Model Context Protocol in Anthropic’s official documentation

Remote MCP

Use our hosted MCP endpoint (recommended)

MCPB Bundle

Single-file bundle for Claude Desktop

Local MCP

Run MCP locally with NPM package

GitHub Repository

View the source code and see detailed documentation
The Linkup MCP server is compatible with any MCP client, such as Cursor or Claude Desktop. Choose between local installation or our hosted endpoint based on your needs.

Features

The Linkup MCP server provides two tools:
  • linkup-search: Real-time web search with natural language queries
    • Standard and deep search modes
    • Domain include/exclude lists, date range filters, max results, and optional image results
    • Access to current information from trusted sources
  • linkup-fetch: Fetch and extract content from any webpage
    • Optional JavaScript rendering for dynamic content
    • Optional image extraction and raw HTML output
    • Perfect for article extraction and content analysis
MCP demo

Remote MCP

Use our hosted MCP endpoint for a quick setup without any local installation. This is the recommended approach for most users.

Prerequisites

To use Remote MCP, you need:
  • A Linkup API key
  • Any MCP client that supports remote MCP over HTTP

Get your API key

Create a Linkup account for free to get your API key.

Authentication

If your MCP client supports custom HTTP headers, prefer sending your API key as:
Authorization: Bearer YOUR_API_KEY
If your client cannot send custom headers, the hosted endpoint also supports the ?apiKey=... query parameter.

Manual Configuration

Install MCP ServerAdd to your ~/.cursor/mcp.json:
{
  "mcpServers": {
    "linkup": {
      "type": "http",
      "url": "https://mcp.linkup.so/mcp?apiKey=YOUR_API_KEY"
    }
  }
}
Replace YOUR_API_KEY with your actual API key. If your client supports custom headers, Authorization: Bearer is preferred over putting the key in the URL.

MCPB Bundle

Download a pre-built MCPB (MCP Bundle) - a self-contained, single-file package that works across compatible MCP clients. This is the recommended approach for Claude Desktop.

What is MCPB?

MCPB (MCP Bundle) is a new format developed by Anthropic for distributing MCP servers. Learn more in the official MCPB documentation.

Download

Quick Download:
curl -L -o linkup-mcp-server.mcpb https://github.com/LinkupPlatform/linkup-mcp-server/releases/latest/download/linkup-mcp-server.mcpb
Or download directly from here.

Installation

1

Download the MCPB file

Use the curl command above or download from GitHub releases.
2

Install in Claude Desktop

Double-click the .mcpb file to install it in Claude Desktop.
3

Configure API Key

When prompted, enter your Linkup API key.

Local MCP

Run the Linkup MCP server locally using NPM.

Prerequisites

  • A Linkup API key
  • Node.js (v24.0.0 or higher)

Get your API key

Create a Linkup account for free to get your API key.

Configuration Examples

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
  "mcpServers": {
    "linkup": {
      "command": "npx",
      "args": ["-y", "linkup-mcp-server", "apiKey=YOUR_LINKUP_API_KEY"]
    }
  }
}
Replace YOUR_LINKUP_API_KEY with your actual API key, then restart your application.
For more configuration examples and advanced usage, see the GitHub README.

Available tools

Once configured, you’ll have access to two tools: Search the web in real time to retrieve current information, facts, and news from trusted sources. Parameters:
  • query (required): Natural language search query. Full questions work best.
  • depth (optional): Search depth - "standard" (default) or "deep"
    • "standard": For queries with direct answers leveraging agentic search (weather, stock prices, simple facts)
    • "deep": For complex research requiring analysis across multiple sources
    The Linkup API also supports a "fast" depth, but the MCP server only exposes "standard" and "deep". If you need "fast", call the API directly via the SDKs or the /search endpoint.
  • includeImages (optional, default false): Return relevant images alongside text results, each with a URL and metadata.
  • includeDomains (optional): Array of domains to restrict results to, e.g. ["bbc.com", "reuters.com"]. Max 100 domains.
  • excludeDomains (optional): Array of domains to exclude from results, e.g. ["reddit.com", "quora.com"].
  • fromDate (optional): Only include content published on or after this date. Format: YYYY-MM-DD.
  • toDate (optional): Only include content published on or before this date. Format: YYYY-MM-DD.
  • maxResults (optional): Maximum number of results to return (positive integer).
Example prompts:
  • “Search for the latest news about AI developments”
  • “What’s the current weather in Tokyo?”
  • “Find information about the new EU AI Act, only from bbc.com and reuters.com, published this year”

linkup-fetch

Fetch and extract content from any webpage URL. Parameters:
  • url (required): The URL to fetch content from
  • renderJs (optional, default false): Whether to render JavaScript content.
    • Enable for dynamic pages that load content via JavaScript
    • Note: the request takes longer to complete
  • extractImages (optional, default false): Extract images found on the page and return them in a dedicated images field. Useful when you need a list of all images for further processing or analysis.
  • includeRawHtml (optional, default false): Include the page’s raw HTML in a dedicated rawHtml field. Useful for custom HTML parsing, preserving specific formatting, or accessing elements that might be filtered out during standard content extraction.
Example prompts:

Troubleshooting

Authentication Format

Important: Current versions of the Linkup MCP server use a different authentication format than v1.x: Correct (v2.x and later):
{
  "args": ["-y", "linkup-mcp-server", "apiKey=YOUR_API_KEY"]
}
Old format (v1.x), no longer supported:
{
  "env": {
    "LINKUP_API_KEY": "YOUR_API_KEY"
  }
}
If you were using v1.x, please update your configuration to the new format.
Need help? Email support@linkup.so, ping us on Discord, or talk to us.