Linkup MCP Server

Linkup MCP server for web search. Exposed over MCP by the linkup mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server that provides web search and page fetching capabilities through Linkup's advanced API. This server enables AI assistants like Claude to perform intelligent web searches with natural language queries and fetch content from any webpage, accessing real-time information from trusted sources across the web.

• 🔍 Real-time Web Search: Search the web for current information, news, and data
• 🧠 Deep Research: Start long-running, multi-source research tasks and poll for results
• 🌐 Page Fetching: Fetch and extract content from any webpage
• 🎯 Natural Language Queries: Use full questions for best results
• 📊 Flexible Search Depth:
• standard - For queries with direct answers

Its toolset

Everything the assistant can do here goes through one of these:

• Cursor — In your ~/.cursor/mcp.json file, add the following: json { "mcpServers": { // ... other MCP servers "linkup": { "type": "http", "url"
• VSCode — Add this to your VS Code MCP config file. See VS Code MCP docs for more info
• Codex — Codex supports both remote HTTP MCP servers and custom HTTP headers via config.toml
• Prerequisites — The Prerequisites tool exposed by this server
• Setup — The Setup tool exposed by this server

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration

You will need 2 environment variables: LINKUP_API_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 24.0.0 - npm

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Linkup's toolset — Cursor, VSCode, Codex and 2 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the linkup mcp server does with a few real requests.