linkup

The Linkup MCP Server exposes two primary MCP tools wired through Linkup's real-time web capabilities. The linkup-search tool lets your AI agent perform live web queries, returning current information, sources, and summaries based on natural language questions. The linkup-fetch tool retrieves content from any given URL and can optionally render JavaScript content to extract dynamic page data. You can combine these tools to search for up-to-date facts and then fetch and summarize relevant pages for deeper context. The server supports different search depths (standard for straightforward answers and deep for multi-source analysis) and can enable JavaScript rendering when needed for dynamic sites.

To use locally via a standard MCP client, configure the server (for example with npx as shown in the installation section) and point your MCP client to this server’s API key-protected endpoint. After setup, invoke the linkup-search tool with a natural-language query like “Search the web for the latest AI developments” or “Find information about the EU AI Act.” For content extraction, use linkup-fetch with a URL such as https://example.com/article to retrieve and summarize page content. You can toggle renderJs on fetch requests when pages rely on client-side rendering for accurate data.

Prerequisites:

• Node.js v18 or newer
• npm (comes with Node.js)

Install and run locally:

1. Ensure Node.js and npm are installed. Verify with: node -v npm -v

2. Install dependencies and set up the MCP server via npx (as described in the README):

# Install dependencies (if you have a local clone)
npm install

# Run the MCP server via npx (uses the remote package)
npx -y linkup-mcp-server apiKey=YOUR_LINKUP_API_KEY

3. If you plan to run via stdio transport or integrate with specific clients, follow the stdio workflow in the README:

npm install
npm run build:stdio
npm run start:stdio apiKey=YOUR_API_KEY

4. For development with Smithery or other MCP clients, use the provided configuration snippet (adjust apiKey accordingly) and ensure the server is reachable by your MCP client.

Prerequisites also include having a valid Linkup API key from your Linkup account.

Tips and notes:

• Replace LINKUP_API_KEY with your actual Linkup API key when configuring the MCP server. You can pass it as a command argument or set it as an environment variable if your client supports it.
• If your queries require up-to-date information (news, stocks, weather), prefer the linkup-search tool with depth set to standard or deep for more thorough analysis.
• Use linkup-fetch with renderJs enabled only for pages that rely on client-side rendering; this can significantly slow down requests.
• When using the stdio transport, you’ll typically run npm run build:stdio once, then start with npm run start:stdio apiKey=YOUR_API_KEY. This setup is suitable for Claude Desktop or other MCP-compatible clients.
• If you encounter connectivity issues, verify that your MCP client is configured to reach the endpoint produced by the npx invocation and that the API key is valid.