A
licenseB
qualityC
maintenanceFacilitates web search capabilities using Perplexity's API, allowing users to retrieve search results through Claude's interface.
1
8
MIT
Claude Web Search MCP Server
by Doriandarko
Клод Веб-поиск MCP-сервер
Этот сервер MCP (Model Context Protocol) предоставляет возможности веб-поиска с использованием API Claude. Он позволяет LLM получать доступ к актуальной информации из сети через стандартизированный интерфейс.
Функции
Инструмент веб-поиска с использованием API веб-поиска Клода
Поддержка фильтрации доменов (разрешенные и заблокированные домены)
Настраиваемое максимальное количество результатов за поиск
Автоматическая настройка из файла конфигурации Claude Desktop
Related MCP server: Google Search MCP
Предпосылки
Node.js 18 или выше
Ключ API Anthropic с включенным веб-поиском
Приложение Claude Desktop для тестирования
Установка и настройка
Клонируйте репозиторий:
git clone https://github.com/Doriandarko/claude-search-mcp.git cd claude-search-mcpУстановить зависимости:
npm installСборка сервера:
npm run buildЭто компилирует код TypeScript и делает сервер исполняемым.
Подключите сервер для глобального доступа:
npm linkЭто делает команду
mcp-server-claude-searchдоступной во всей системе, позволяя приложению Claude Desktop находить ее.
Запуск сервера с помощью приложения Claude Desktop
После установки и подключения сервера приложение Claude Desktop может управлять им автоматически, если оно правильно настроено.
Настройте приложение Claude Desktop: Откройте файл конфигурации сервера MCP приложения Claude Desktop (обычно
claude_desktop_config.json). Добавьте или обновите запись для этого сервера:{ "mcpServers": { // ... other servers ... "claude-search": { "command": "mcp-server-claude-search", "env": { "ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE" } } // ... other servers ... } }Замените
"YOUR_ANTHROPIC_API_KEY_HERE"на ваш фактический ключ Anthropic API. Сервер также попытается прочитать этот ключ из~/code/claude-search-mcp/claude_desktop_config.jsonесли переменнаяenvздесь не задана, но хорошей практикой является определение ее для каждого сервера в основной конфигурации.Запустите приложение Claude Desktop: Запустите (или перезапустите) приложение Claude Desktop. Теперь оно должно найти и запустить
mcp-server-claude-searchпри необходимости.Используйте веб-поиск: теперь вы можете использовать возможности веб-поиска в своих беседах с Клодом.
Ручное выполнение сервера (для тестирования/разработки)
Если вы хотите запустить сервер вручную для целей тестирования или разработки (вне управления приложением Claude Desktop):
Использование глобально связанной команды:
mcp-server-claude-searchНепосредственно с помощью tsx (для разработки с автоматическим перезапуском):
npm run devЗапуск скомпилированного кода напрямую:
npm start
Параметры инструмента веб-поиска
Инструмент веб-поиска поддерживает следующие параметры при вызове LLM:
query(обязательно): Строка поискового запроса.maxResults(необязательно): максимальное количество возвращаемых результатов поиска (по умолчанию: 5).allowedDomains(необязательно): массив доменов для включения в результаты поиска (например,["example.com", "wikipedia.org"]).blockedDomains(необязательно): Массив доменов, которые следует исключить из результатов поиска.
Лицензия
Массачусетский технологический институт
Available Tools
1 toolweb_searchA
Search the web for real-time information about any topic. Use this tool when you need up-to-date information that might not be available in your training data, or when you need to verify current facts.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The search query to look up on the web | |
| maxResults | No | Maximum number of search results to return (default: 5) | |
| allowedDomains | No | Only include results from these domains | |
| blockedDomains | No | Never include results from these domains |
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the tool's purpose and usage context but lacks details on behavioral traits such as rate limits, authentication needs, or specific output format. The description does not contradict any annotations, but it could be more informative about operational constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded and concise, consisting of two sentences that directly address purpose and usage guidelines without unnecessary details. Every sentence earns its place by providing essential information efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (web search with 4 parameters) and no output schema, the description is adequate but could be more complete. It covers purpose and usage well but lacks details on behavioral aspects like result format or limitations. With no annotations, it should ideally provide more context to fully guide the agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, so the schema already documents all parameters well. The description does not add any parameter-specific information beyond what the schema provides, such as examples or additional context. This meets the baseline for high schema coverage, but no extra value is added.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with specific verbs ('search the web') and resources ('real-time information about any topic'). It distinguishes the tool's function from potential alternatives by emphasizing real-time, up-to-date information that might not be in training data, which is essential for a web search tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use this tool: 'when you need up-to-date information that might not be available in your training data, or when you need to verify current facts.' This provides clear context and guidance for the agent, even though no sibling tools are listed, making it comprehensive for decision-making.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
web_search
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
Related MCP Connectors
Provides AI assistants with access to Seltz's powerful Web Search capabilities.
Web search and page-reading for AI agents. One-click OAuth connect, or a Caesar API key.
Web search, browser automation, scraping, crawling and CAPTCHA solving for AI agents.
The best web search for your AI Agent
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables Large Language Models to perform real-time web searches using Google Custom Search API. Integrates with Claude Desktop to retrieve current information from the internet.1MIT
- AlicenseNot gradedqualityDmaintenanceExposes 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
- AlicenseNot gradedqualityDmaintenanceEnables web search via Brave Search API with freshness filters, full page content fetching, and usage tracking. Designed for Claude integration.399 npmGPL 3.0