Skip to main content
Glama
MissionSquad

@missionsquad/mcp-searxng-puppeteer

Official
by MissionSquad
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

SearXNG + Puppeteer MCP Server

An MCP server implementation that integrates the SearXNG API for powerful web search capabilities and uses @missionsquad/puppeteer-scraper to read and process live web content.

This server is a component of the Mission Squad ecosystem, designed to provide reliable, agentic web browsing and information retrieval.

Features

  • Web Search: Perform general queries, find news, and access articles with robust filtering.

  • URL Content Reading: Scrape and process content from any URL, returning clean text.

  • Pagination: Control which page of search results to retrieve.

  • Time Filtering: Filter search results by time range (day, month, year).

  • Language Selection: Filter results by preferred language.

  • Safe Search: Control the content filtering level for search results.

Related MCP server: SearXNG MCP Server

Tools

web_search

Executes a web search using the configured SearXNG instance.

Inputs:

  • query (string, required): The search query.

  • pageno (number, optional): The search result page number to retrieve. Starts at 1. Defaults to 1.

  • count (number, optional): The number of results to return per page. Defaults to 10.

  • time_range (string, optional): Filters results by time range. Valid options are: "day", "month", "year".

  • language (string, optional): The language code for results (e.g., "en", "fr", "de"). Defaults to the instance's setting.

  • safesearch (string, optional): The safe search filter level. Valid options are: "0" (None), "1" (Moderate), "2" (Strict). Defaults to the instance's setting.

get_url_content

Reads the content from a given URL, processes it with Puppeteer, and returns the text content.

Inputs:

  • url (string, required): The URL to fetch and process.

Configuration

Setting the SEARXNG_URL

This server requires a running SearXNG instance.

  1. Choose a SearxNG instance from the list of public instances or deploy your own.

  2. Set the SEARXNG_URL environment variable to the instance's URL.

  3. If not set, the server defaults to http://localhost:8080.

Running SearXNG with Docker

You can run SearXNG locally using Docker.

Docker Run Command:

docker run --rm -d -p 8080:8080 -v ${PWD}/searxng:/etc/searxng:rw --name searxng searxng/searxng:latest

This command will start a SearXNG container and map it to port 8080 on your local machine.

Docker Compose Example:

Create a docker-compose.yml file with the following content:

services:
  searxng:
    container_name: searxng
    image: docker.io/searxng/searxng:latest
    restart: unless-stopped
    ports:
      - 8081:8080
    volumes:
      - ./searxng:/etc/searxng:rw
    environment:
      - SEARXNG_BASE_URL=https://${SEARXNG_HOSTNAME:-localhost}/
      - UWSGI_WORKERS=${SEARXNG_UWSGI_WORKERS:-4}
      - UWSGI_THREADS=${SEARXNG_UWSGI_THREADS:-4}
    cap_drop:
      - ALL
    cap_add:
      - CHOWN
      - SETGID
      - SETUID
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: "2"

Run docker-compose up -d to start the service. Note that this example maps the service to port 8081.

Usage

NPX

To run the server directly for development or testing:

{
  "mcpServers": {
    "searxng-puppeteer": {
      "command": "npx",
      "args": ["-y", "@missionsquad/mcp-searxng-puppeteer"],
      "env": {
        "SEARXNG_URL": "YOUR_SEARXNG_INSTANCE_URL"
      }
    }
  }
}

NPM

Install the package globally:

npm install -g @missionsquad/mcp-searxng-puppeteer

And then configure it in your MCP client:

{
  "mcpServers": {
    "searxng-puppeteer": {
      "command": "mcp-searxng-puppeteer",
      "env": {
        "SEARXNG_URL": "YOUR_SEARXNG_INSTANCE_URL"
      }
    }
  }
}

Docker

A Docker image will be available on Docker Hub soon. To build it locally:

docker build -t missionsquad/mcp-searxng-puppeteer:latest .

Then, add it to your MCP client configuration:

{
  "mcpServers": {
    "searxng-puppeteer": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "SEARXNG_URL",
        "missionsquad/mcp-searxng-puppeteer:latest"
      ],
      "env": {
        "SEARXNG_URL": "YOUR_SEARXNG_INSTANCE_URL"
      }
    }
  }
}

Try it on Mission Squad

You can test the @missionsquad/mcp-searxng-puppeteer server and other MCP servers on the Mission Squad platform. Mission Squad is an Agentic AI Platform that allows you to build, manage, and deploy cooperative agents that connect to any model, leverage private data, and automate complex tasks. Sign up for a free account to get started.

License

This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.

Available Tools

2 tools
get_url_contentA

Get the content of a URL. Use this for further information retrieving to understand the content of each URL.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL

TDQS

A3.5/5.0
Behavior2/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 of behavioral disclosure. It states the tool retrieves content but lacks details on behavioral traits like error handling (e.g., for invalid URLs), authentication needs, rate limits, or output format (e.g., text, HTML). This leaves significant gaps for an agent to understand how the tool behaves in practice.

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 appropriately sized and front-loaded: the first sentence states the core purpose, and the second provides usage context. Both sentences earn their place by adding value without redundancy, making it efficient and easy to parse for an agent.

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 low complexity (1 parameter, no output schema, no annotations), the description is moderately complete. It covers purpose and usage but lacks details on behavioral aspects like error handling or output format, which are important for a content retrieval tool. Without annotations or output schema, more context would improve completeness.

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, with the 'url' parameter documented as 'URL'. The description adds no additional meaning beyond this, as it doesn't specify URL format constraints (e.g., must be valid HTTP/HTTPS) or usage examples. With high schema coverage, the baseline is 3, and the description doesn't compensate with extra insights.

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

Purpose4/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: 'Get the content of a URL' specifies the verb (get) and resource (URL content). It distinguishes from the sibling 'web_search' by focusing on retrieving content from a specific URL rather than searching the web. However, it doesn't specify the exact nature of the content (e.g., HTML, text, metadata), which prevents a perfect score.

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

Usage Guidelines4/5

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

The description provides clear usage context: 'Use this for further information retrieving to understand the content of each URL' indicates when to use it—for analyzing URL content. It implicitly distinguishes from 'web_search' by focusing on specific URLs rather than search queries. However, it lacks explicit exclusions or alternatives, such as when not to use it (e.g., for invalid URLs or rate-limited sites).

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. Dates show when Glama detected each change.

  1. 2 tool updates
    • First observedget_url_content
    • First observedweb_search
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: 'get_url_content' retrieves content from a specific URL, while 'web_search' performs broad searches across the web. There is no overlap or ambiguity between them, making it easy for an agent to select the appropriate tool based on the task.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern ('get_url_content' and 'web_search'), using snake_case throughout. This predictability aids in understanding and usage without any deviations or mixed conventions.

Tool Count2/5

With only 2 tools, the server feels thin for its apparent scope of web search and content retrieval. While the tools cover basic operations, the count is too low for a comprehensive web interaction toolset, lacking features like advanced search filters, content analysis, or URL management.

Completeness2/5

The tool surface is severely incomplete for a web search and content retrieval domain. It provides search and URL fetching but lacks essential operations such as filtering search results, handling pagination, analyzing content (e.g., summarization), or managing search history, which are common in similar toolsets.

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

Related MCP Servers

  • SearXNG MCP Server

    tobioffice
    A
    license
    B
    quality
    D
    maintenance
    An MCP server that integrates with the SearXNG API to provide comprehensive web search capabilities with features like time filtering, language selection, and safe search. It also enables users to fetch and convert web content from specific URLs into markdown format.
    2
    22
    4
    MIT

  • mcp-searxng

    atomlong
    A
    license
    A
    quality
    B
    maintenance
    An MCP server that integrates the SearXNG API for web search and URL content extraction with advanced features like pagination, caching, and proxy support.
    4
    14,640
    2
    MIT

Appeared in Searches

Latest Blog Posts

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/MissionSquad/mcp-searxng'

If you have feedback or need assistance with the MCP directory API, please join our Discord server