# Linkup MCP server

> Search the web in real time, run deep research tasks and fetch page content with sourced answers.

- Listing: https://mcp.tc/i/linkup
- Connect: use the server's own URL `https://mcp.linkup.so/mcp` (with your API key); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: API key
- Category: [Search & Web Data](https://mcp.tc/c/search-web)
- Vendor: Linkup
- Homepage: <https://docs.linkup.so/pages/integrations/mcp/mcp>
- Repository: <https://github.com/LinkupPlatform/linkup-mcp-server>
- Package: npm `linkup-mcp-server`

## About

Linkup connects an assistant to the Linkup web search API. It can search the web with natural language queries, filter by domain and date, run long multi-source research tasks, and fetch the content of a given webpage, with answers backed by sources.

The hosted endpoint at https://mcp.linkup.so/mcp uses Streamable HTTP and needs a Linkup API key, sent as a Bearer token in the Authorization header or as an apiKey query parameter. It can also run locally over stdio with npx (linkup-mcp-server) or as an MCP bundle for Claude Desktop.

## What it can do

- Search the web in real time with standard or deep depth
- Filter results by included or excluded domains and date range
- Include image results in searches
- Start long-running research tasks and poll for results
- Fetch and extract content from any webpage
- Render JavaScript or return raw HTML when fetching pages

## Example prompts

- "Search the web for the latest news about the EU AI Act."
- "Compare 2024 cloud revenue growth of Microsoft, Amazon and Google."
- "Fetch https://example.com/article and summarize it."
- "Find recent reports on NVIDIA's stock price, only from reuters.com."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http linkup https://mcp.linkup.so/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
```

2. Replace the placeholder with your key before you run it, then check it with `/mcp` inside Claude Code.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Custom connectors can’t send this server’s key header, so use the `mcp-remote` bridge. Open **Settings → Developer → Edit Config** and add:

`claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "linkup": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.linkup.so/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}
```

2. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=linkup&config=eyJ1cmwiOiJodHRwczovL21jcC5saW5rdXAuc28vbWNwIiwiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyIDxZT1VSX0FQSV9LRVk%2BIn19>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "linkup": {
      "url": "https://mcp.linkup.so/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

### VS Code

Add it to `.vscode/mcp.json`. VS Code asks for the key the first time and stores it securely:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "linkup": {
      "type": "http",
      "url": "https://mcp.linkup.so/mcp",
      "headers": {
        "Authorization": "Bearer ${input:api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "api-key",
      "description": "API key",
      "password": true
    }
  ]
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "linkup": {
      "serverUrl": "https://mcp.linkup.so/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add linkup --url https://mcp.linkup.so/mcp --bearer-token-env-var LINKUP_API_KEY
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.linkup]
url = "https://mcp.linkup.so/mcp"
bearer_token_env_var = "LINKUP_API_KEY"
```

Set `LINKUP_API_KEY` to your key in the shell that runs Codex.

### Gemini CLI

```bash
gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" linkup https://mcp.linkup.so/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "linkup": {
      "type": "http",
      "url": "https://mcp.linkup.so/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.linkup.so/mcp`.

## Details

- Server version: 0.0.1
- Last checked: 2026-10-03 (not reachable)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/linkup (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report