Linkup

MCP server by Linkup

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

Needs an API key (Needs an API key from the vendor)Streamable HTTPLast check failed

Connect to Linkup

Linkup needs an API key. Connect with its own URL and your key:

https://mcp.linkup.so/mcp

Send your key in the Authorization header. mcp.tc never sees or stores keys. Where to get a key

Linkup didn’t answer our last check on 3 Oct 2026. It may be down for now.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/linkup

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 you 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

Tools

Linkup lists its tools only to clients with a key, so we can’t show them here.

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.

Set up

Every client connects to mcp.linkup.so. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http linkup https://mcp.linkup.so/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
  1. 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
{
  "mcpServers": {
    "linkup": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.linkup.so/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}
  1. Replace the placeholder with your key and restart Claude Desktop.

The bridge needs Node.js on your computer.

Cursor

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

mcp.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
{
  "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
{
  "mcpServers": {
    "linkup": {
      "serverUrl": "https://mcp.linkup.so/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade.

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

Codex

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
[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

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.

{
  "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.

FAQ

Can I paste mcp.tc/i/linkup into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.linkup.so/mcp, so your client talks to Linkup directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Linkup need an API key or a sign-in?

Yes. Linkup needs an API key, sent as the Authorization header. Get one from Linkup and keep it in your client’s config, never in a shared file.

Is Linkup a remote or a local server?

Remote. Linkup hosts it at https://mcp.linkup.so/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Linkup do?

You can search the web in real time with standard or deep depth, filter results by included or excluded domains and date range and include image results in searches.

Which clients can use it?

Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others, and Claude Desktop through the mcp-remote bridge. claude.ai and ChatGPT can’t send a key, so they can’t use it.

Who wrote this page?

mcp.tc’s robot read Linkup’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

Embed

Show Linkup in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Linkup on mcp.tc](https://mcp.tc/i/linkup/badge.svg)](https://mcp.tc/i/linkup)
HTML
<a href="https://mcp.tc/i/linkup"><img src="https://mcp.tc/i/linkup/badge.svg" alt="Linkup on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/linkup.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/linkup" title="Linkup on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/linkup.json

What each field means

mcp.tc isn’t affiliated with Linkup. This page was built from Linkup’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.