Skip to main content
Glama
deenesjakoruzh
Doriandarko

Claude Web Search MCP Server

by Doriandarko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Claude Web Search MCP Server

This MCP (Model Context Protocol) server provides web search capabilities using the Claude API. It allows LLMs to access up-to-date information from the web through a standardized interface.

Features

  • Web search tool using Claude's web search API

  • Support for domain filtering (allowed and blocked domains)

  • Configurable maximum results per search

  • Automatic configuration from Claude Desktop config file

Related MCP server: Google Search MCP

Prerequisites

  • Node.js 18 or higher

  • An Anthropic API key with web search enabled

  • Claude Desktop app for testing

Installation & Setup

  1. Clone the repository:

    git clone https://github.com/Doriandarko/claude-search-mcp.git
cd claude-search-mcp

  2. Install dependencies:

    npm install

  3. Build the server:

    npm run build

    This compiles the TypeScript code and makes the server executable.

  4. Link the server for global access:

    npm link

    This makes the mcp-server-claude-search command available system-wide, allowing the Claude Desktop app to find it.

Running the Server with Claude Desktop App

Once the server is installed and linked, the Claude Desktop app can manage it automatically if configured correctly.

  1. Configure Claude Desktop App: Open your Claude Desktop app's MCP server configuration file (usually claude_desktop_config.json). Add or update the entry for this server:

    {
  "mcpServers": {
    // ... other servers ...
    "claude-search": {
      "command": "mcp-server-claude-search",
      "env": {
        "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE"
      }
    }
    // ... other servers ...
  }
}

    Replace "YOUR_ANTHROPIC_API_KEY_HERE" with your actual Anthropic API key. The server will also attempt to read this key from ~/code/claude-search-mcp/claude_desktop_config.json if the env variable is not set here, but it's good practice to define it per-server in the main config.

  2. Launch Claude Desktop App: Start (or restart) your Claude Desktop application. It should now be able to find and launch the mcp-server-claude-search when needed.

  3. Use Web Search: You can now use web search capabilities in your conversations with Claude.

Manual Server Execution (for testing/development)

If you want to run the server manually for testing or development purposes (outside of the Claude Desktop app management):

  • Using the globally linked command:

    mcp-server-claude-search

  • Directly with tsx (for development with auto-restart):

    npm run dev

  • Running the compiled code directly:

    npm start

Web Search Tool Parameters

The web search tool supports the following parameters when called by an LLM:

  • query (required): The search query string.

  • maxResults (optional): Maximum number of search results to return (default: 5).

  • allowedDomains (optional): Array of domains to include in search results (e.g., ["example.com", "wikipedia.org"]).

  • blockedDomains (optional): Array of domains to exclude from search results.

License

MIT

Available Tools

1 tool

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedweb_search
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it against. The single tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

The single tool name 'web_search' follows a consistent verb_noun pattern, and since there are no other tools, there is no inconsistency to evaluate. The naming is straightforward and appropriate for its function.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and can feel thin or incomplete. For a web search server, while the core function is covered, additional tools like advanced search filters or result management might be expected to enhance utility.

Completeness3/5

The server provides a basic search function, which covers the essential need for real-time information retrieval. However, there are notable gaps, such as lack of tools for refining searches, handling pagination, or accessing specific types of content, which could limit agent effectiveness in complex scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Perplexity MCP Server

    jaacob
    A
    license
    B
    quality
    D
    maintenance
    Facilitates web search capabilities using Perplexity's API, allowing users to retrieve search results through Claude's interface.
    1
    8
    MIT

  • Perplexity MCP Server

    shaunmacfullstack
    A
    license
    Not graded
    quality
    D
    maintenance
    Exposes Perplexity AI's search capabilities to Claude, enabling real-time web search and information retrieval within the assistant. The project is currently in active development with plans to support Perplexity Spaces and multi-source data synthesis.
    Apache 2.0

  • Brave Search MCP Server

    cuer-bot
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables web search via Brave Search API with freshness filters, full page content fetching, and usage tracking. Designed for Claude integration.
    128 npm
    GPL 3.0

Appeared in Searches