Get the FREE Ultimate OpenClaw Setup Guide →

deep-search

A deep web search MCP using LinkUp API.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio joaomj-deep-search-mcp node /home/joao/Cline/MCP/linkup-mcp-server/build/index.js \
  --env LINKUP_API_KEY="your-api-key-here"

How to use

Deep Search MCP Server provides a dedicated tool for performing deep web searches via the LinkUp API. It exposes a deep_search tool that accepts a required query string and an optional max_results parameter (default is 5). When invoked, it queries the LinkUp API and returns structured search results suitable for downstream consumption or display. Use this MCP server to integrate deep web search capabilities into your MCP workflows or applications that rely on LinkUp data.

To use the deep_search tool, supply the query string you want to search for. Optionally, you can set max_results to limit how many results are returned. The server will handle authentication via the configured LINKUP_API_KEY environment variable and return the results in a structured format compatible with MCP tooling.

How to install

Prerequisites:

  • Node.js and npm installed on your system
  • Access to the MCP server project source

Installation steps:

  1. Install dependencies
npm install
  1. Build the server
npm run build
  1. Configure the MCP server in your settings (example shown in README)
{
  "mcpServers": {
    "deep-search-mcp": {
      "command": "node",
      "args": ["/home/joao/Cline/MCP/linkup-mcp-server/build/index.js"],
      "env": {
        "LINKUP_API_KEY": "your-api-key-here"
      }
    }
  }
}
  1. Run for development with auto-rebuild (optional)
npm run watch
  1. Run in production (optional)
npm start

Additional notes

Tips and considerations:

  • Ensure you have a valid LINKUP_API_KEY from the LinkUp API service and keep it secure (do not commit to source control).
  • The deep_search tool accepts a required query string and an optional max_results parameter; if omitted, a default of 5 results is used.
  • Debugging MCP servers over stdio can be challenging; consider using the MCP Inspector tool for easier inspection.
  • If you plan to deploy, consider adding caching, pagination, and rate limiting as suggested in the README's Next Steps.
  • Confirm the built index.jsx path in the deployment environment matches the configured build output.

Related MCP Servers

Sponsor this space

Reach thousands of developers