Which integrations are available for this server?

Enables web search functionality using DuckDuckGo's HTML interface without requiring an API key, returning search results with titles and URLs. Provides web search capabilities through SerpAPI's Google search integration when an API key is configured, returning search results with titles and URLs.

How do I use MCP Web Tools Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Web Tools Server search for latest AI developments" 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.

MCP Web Tools Server

by JoaoPedroLanca

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

MCP Web Tools Server (Node.js)

⭐ If you find this useful, please consider giving it a star!

MCP (Model Context Protocol) server for LM Studio that provides tools for internet connectivity:

search_web: searches the web and returns titles and URLs
fetch_url: performs HTTP GET and returns content-type and body (limited)
extract_readable: extracts the main readable content from a page

Requirements

Node.js 18+

Installation

npm install

Execution (stdio mode)

npm start

The server uses stdio (required for integration with LM Studio via MCP).

Environment variables (optional)

SERPAPI_KEY: if provided, the search_web tool will use SerpAPI (Google). Otherwise, leave the field empty to use DuckDuckGo (HTML) without a key.

LM Studio Configuration

Add a custom MCP server pointing to this project's command. In LM Studio, go to Program → Install → Edit mcp.json, and paste the json below:

{
  "mcpServers": {
    "mcp-web-tools-server": {
      "command": "npm",
      "args": [
        "run",
        "start",
        "--silent"
      ],
      "cwd": "C:/mcp-web-tools",
      "env": {
        "SERPAPI_KEY": ""
      }
    }
  }
}

In "cwd" put the project Path

Available tools

search_web:
- input: { "query": string, "limit?": number (1..10) }
- output: text with numbered list (title and URL)
fetch_url:
- input: { "url": string, "maxBytes?": number (up to 8MB) }
- output: two text blocks: metadata (contentType/bytes) and truncated body
extract_readable:
- input: { "url": string }
- output: text with title, byline, summary and main content

Getting Started

Clone the repository:

git clone https://github.com/JoaoPedroLanca/mcp-web-tools.git
cd mcp-web-tools
npm install
npm start

Download ZIP

Notes

Very large responses are truncated (16MB by default) to avoid exceeding client limits.
search_web without a key uses DuckDuckGo HTML; results may vary and are subject to site changes.

Available Tools

3 tools

extract_readableD

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fetch_urlD

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes
`maxBytes`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_webD

ParametersJSON Schema

Name	Required	Description	Default
`query`	Yes
`limit`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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.

3 tool updatesv1.0.0Jan 3, 2026
- Changedextract_readable2 fields changed
  - addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
  - addedInput schema / additionalProperties
```
Added value: +false
```
- Changedfetch_url2 fields changed
  - addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
  - addedInput schema / additionalProperties
```
Added value: +false
```
- Changedsearch_web2 fields changed
  - addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
  - addedInput schema / additionalProperties
```
Added value: +false
```
3 tool updatesNov 2, 2025
- First observedextract_readable
- First observedfetch_url
- First observedsearch_web

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

D1.6/5.0

Scored 2026-04-18 08:15 across 3 tools

Disambiguation3/5

The tools have distinct primary actions (extract, fetch, search), but without descriptions, their exact scopes and potential overlaps are unclear. An agent might confuse when to use fetch_url versus search_web if both involve web retrieval, but the verb differences provide some guidance.

Naming Consistency4/5

All tool names follow a consistent verb_noun pattern with snake_case (extract_readable, fetch_url, search_web), making them predictable and readable. There are no deviations in naming style across the set.

Tool Count3/5

With only 3 tools, the set feels thin for a 'Web Tools Server', suggesting it might lack coverage for common web operations like parsing or interacting with content. However, the count is not extreme and could be appropriate if these are core utilities.

Completeness2/5

Inferred domain is web-related utilities, but the surface is severely incomplete: missing obvious tools for actions like parsing HTML, handling cookies, or managing sessions. The three tools provide basic fetch, extract, and search functions, but leave significant gaps for comprehensive web tooling.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

agentsearch-mcp A
io.github.IsaiahDupree
LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.
Search RAG Systems Browser Automation
31
Brainiall Web A
com.brainiall
Web search, URL content extraction to Markdown, site mapping, and recursive web crawler.
Browser Automation Web Scraping
1
Sofya A
co.sofya
Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.
Search Browser Automation Web Scraping
42
Nimrod ResearchOAuth
ai.orchis
Web research for agents: quality-scored Google search, webpage extraction, and deep research.
Browser Automation Search Web Scraping
1256

Related MCP Servers

DuckDuckGo MCP Server
Search Browser Automation Web Scraping
trustgraph-ai
F
license
Not graded
quality
C
maintenance
Enables web searching through DuckDuckGo and fetching content from webpages. Provides search capabilities with configurable result limits and webpage content extraction for AI assistants.
Updated 3 months ago (2026-07-01 08:48 UTC)
-
DuckDuckGo MCP Server
Search Browser Automation Web Scraping
988664li-star
A
license
B
quality
D
maintenance
Enables web search through DuckDuckGo and webpage content fetching with intelligent text extraction. Features built-in rate limiting and LLM-optimized result formatting for seamless integration with language models.
Updated a year ago (2025-10-18 07:33 UTC)
2
MIT
Web Search MCP
Search Web Scraping Browser Automation
pranavms13
A
license
Not graded
quality
D
maintenance
Enables web searching through Google, DuckDuckGo, and Bing using a headless Chrome browser, returning structured results with titles, URLs, and snippets. Also supports fetching and extracting text content from any webpage.
Updated 4 months ago (2026-06-01 18:24 UTC)
14
MIT
MCP DuckDuckGo
Browser Automation Web Scraping Search
AstroCorp
A
license
Not graded
quality
D
maintenance
Enables AI assistants to search the internet using DuckDuckGo and extract clean, formatted content from web pages.
Updated 8 months ago (2026-01-28 19:15 UTC)
194 npm
GPL 3.0

Appeared in Searches

A tool for writing to files and searching the web