Linkup Model Context Protocol

Created By
LinkupPlatforma year ago
Javascript version of the Linkup MCP server.
Overview

what is Linkup Model Context Protocol?

Linkup Model Context Protocol (MCP) is a JavaScript server that integrates Linkup's web search functionality with AI models that support function calling through the Model Context Protocol.

how to use Linkup MCP?

To use the Linkup MCP server, you can run it directly using npx with your Linkup API key, or set the API key as an environment variable. For example:

npx -y linkup-mcp-server --api-key=YOUR_LINKUP_API_KEY

key features of Linkup MCP?

  • Integration with AI models for enhanced web search capabilities.
  • Command line options for customization, including API key and base URL.
  • Compatibility with Claude AI for seamless operation.

use cases of Linkup MCP?

  1. Enhancing AI models with real-time web search data.
  2. Building applications that require dynamic information retrieval.
  3. Supporting developers in creating AI-driven solutions with web search integration.

FAQ from Linkup MCP?

  • What is the purpose of the Linkup MCP server?

It serves to connect AI models with web search functionalities, allowing for more informed responses.

  • Is there a cost associated with using Linkup MCP?

The usage is tied to your Linkup API key, which may have associated costs depending on your plan.

  • Can I customize the API base URL?

Yes, you can set a custom API base URL using the --base-url option.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
LinkupPlatform
Star
3
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago