Linkup MCP Server
Linkup MCP server: real-time web search, page fetching and long research tasks with sources for an agent
- 29 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Agent queries and page addresses go to the Linkup service
- The API key travels in a header and can land in logs when passed as a URL parameter
Install
- Works in
Manual install
{"mcpServers":{"linkup":{"type":"http","url":"https://mcp.linkup.so/mcp?apiKey=LINKUP_API_KEY"}}}The hosted server from the README; pass the key in an Authorization: Bearer header if the client can.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Agent queries and page addresses go to the Linkup service
- The API key travels in a header and can land in logs when passed as a URL parameter
This is third-party code. Review the repository files before installing.
What it does
The Linkup server gives an agent access to the internet through the Linkup service API. The linkup-search tool searches by a natural-language query in two depth modes: standard for questions with a direct answer and deep for comparisons across several sources. Results are narrowed with includeDomains and excludeDomains lists, a date range with fromDate and toDate, and a maxResults count. Images can be requested. The linkup-fetch tool pulls page content, optionally with JavaScript rendering, an image list and raw HTML. For questions one search cannot answer there is the linkup-research and linkup-get-research pair: the first starts an autonomous investigation and returns an id, and the second polls the task until completed or failed. The modes answer, investigate and research set the kind of result, and reasoningDepth from S to XL sets the time spent. The server is hosted at https://mcp.linkup.so/mcp, and a local run through npx is available. A ready MCPB package is published for Claude Desktop.
Who it is for. Developers and researchers who need fresh news, prices and facts in the answers of Claude Code, Cursor or Codex instead of the model's built-in knowledge.
Good fit when
- You need to learn how a new EU regulation affects startups and get an answer with sources
- A year-over-year revenue comparison for three companies' cloud units runs through linkup-research
- Search is limited to Reuters and BBC for the past week
- An article with dynamic loading is read through linkup-fetch with renderJs on
- The agent checks a current price and availability before recommending a product
Not a fit when
- You want search with no key and no external service: Linkup needs an API key
- The data sits behind a login or in a closed network: the server reads public pages only
- You need an answer within seconds at every step: research takes minutes
- Queries contain confidential text: they go to a third-party service
Example request
Find how the EU AI Act affects startups and give an answer with sources no older than six months.MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
LINKUP_API_KEYrequired, secret- Linkup API key from the app.linkup.so dashboard.
Limitations
A Linkup API key is required, and a free account is created in the dashboard. If the client can send headers, pass the key in Authorization: Bearer and keep the apiKey URL parameter for clients that cannot. A linkup-research task usually takes several minutes, and polling more often than once a second is rate-limited. Developing the server itself needs Node.js 24 or newer. Availability of Linkup from Russia was not checked.
How to disable. Remove the server from the client: claude mcp remove linkup, the linkup entry in mcp.json or the table in Codex config.toml. Revoke the key at app.linkup.so.
FAQ
How do I connect Linkup MCP to Cursor or Codex?
For Cursor add a linkup server of type http with https://mcp.linkup.so/mcp to mcp.json. For Codex set url and bearer_token_env_var = LINKUP_API_KEY in config.toml. The local variant starts with npx -y linkup-mcp-server apiKey=LINKUP_API_KEY.
Where do I get an API key?
Create a free account at app.linkup.so and copy the key from the dashboard.
How is standard different from deep?
Standard fits questions with a direct answer: weather, rates, simple facts. Deep is for complex queries that analyze several sources.
How does long research work?
The agent starts linkup-research and receives a task id, then polls linkup-get-research until the status is completed or failed. The result sits in the output field and the failure reason in the error field.
Can it read JavaScript pages?
Yes. linkup-fetch accepts renderJs. The request gets slower, but dynamically loaded content reaches the response.
Discussion
No questions or reviews yet.
Related
MCP serversA unified search MCP server: one interface to Tavily, Brave, Kagi, Exa, Linkup, Firecrawl and GitHub search
GPT Researcher MCP
GPT Researcher MCP Server
An MCP server for deep web research: GPT Researcher vets sources on its own and hands the agent a ready report
MCP server for real-time web search: general and vertical search, batch queries and page content extraction
A web search MCP server that gives the agent full page text at once: Stack Overflow answers, GitHub threads, arXiv papers
Web search via DuckDuckGo and page reading for the agent with no API keys, with built-in rate limiting
Official Tavily MCP server: real-time web search, page content extraction, site mapping and crawling
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Linkup MCP Server (this card) | yes | API key | 29 | |
| Tavily MCP Server | yes | API key | 2,477 | also covers search and page reading, but without a pair for long autonomous research |
| Exa MCP Server | yes | OAuth | 5,213 | gives search and research through Exa Agent, another source and another parameter set |
| Brave Search MCP Server | yes | API key | 1,562 | searches the web, news, images, videos and places on the Brave index |
README in short
The README gives connection methods for Cursor, VS Code and Codex, an MCPB package for Claude Desktop and a local stdio run. It then describes the four tools with their parameters and example queries, and ends with development commands and debugging through MCP Inspector.