A
licenseB
qualityD
maintenanceFacilitates web search capabilities using Perplexity's API, allowing users to retrieve search results through Claude's interface.
1
7
MIT
Claude Web Search MCP Server
by Doriandarko
The Claude Web Search MCP Server enables LLMs to perform web searches through the Claude API, providing access to real-time information from the internet.
Key capabilities:
Perform web searches with specific queries to retrieve up-to-date information
Verify current facts that may not be available in training data
Customize search parameters:
Set maximum number of results returned (default: 5)
Filter results using
allowedDomainsandblockedDomains
Integration with Claude Desktop app for automatic management
Option to run manually for testing or development purposes
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Claude Web Search MCP Serversearch for latest AI developments from reputable tech news sites"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Clone the repository:
git clone https://github.com/Doriandarko/claude-search-mcp.git cd claude-search-mcpInstall dependencies:
npm installBuild the server:
npm run buildThis compiles the TypeScript code and makes the server executable.
Link the server for global access:
npm linkThis makes the
mcp-server-claude-searchcommand 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.
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.jsonif theenvvariable is not set here, but it's good practice to define it per-server in the main config.Launch Claude Desktop App: Start (or restart) your Claude Desktop application. It should now be able to find and launch the
mcp-server-claude-searchwhen needed.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-searchDirectly with tsx (for development with auto-restart):
npm run devRunning 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 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.
TDQS
A4/5.0
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
ResponsivenessSyncing
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
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.
Live SEO workflow tools for Claude Code, Codex, and 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 gradedqualityFmaintenanceProvides real-time Google search capabilities to AI assistants like Claude, bypassing anti-scraping mechanisms.14621MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Doriandarko/claude-search-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server