MMNT

MCP server for Mamont search engine
  • typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "zbkm-mmnt-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mmnt-mcp-server"
      ]
    }
  }
}

This MCP server provides an interface to run Mamont search engine actions through MCP clients. It enables you to perform searches and retrieve cached results in a standardized way, helping your systems integrate Mamont data and capabilities efficiently.

How to use

You interact with this server through an MCP client to perform search queries and access cached pages. Two core tools are exposed: mmnt_search for running a search on the Mamont engine and mmnt_cache for retrieving a page from the search page cache. Use the client to submit a query string and a page number with mmnt_search, and use a cache identifier with mmnt_cache to fetch text or full HTML as needed.

Operational pattern: start the MCP server locally and point your MCP client at it. You will send requests to the server using the client’s standard MCP workflow. The server handles the following inputs: mmnt_search accepts a query and a page; mmnt_cache accepts an id and a flag to return only text. You can compose these calls to implement features like keyword search, result paging, and quick content extraction from cached pages.

How to install

Prerequisites: ensure you have Node.js (and npm or corepack) installed on your system.

Install and run the MCP server using the following command. This uses npx to run the mmnt-mcp-server package directly.

{
  "mcpServers": {
    "mmnt": {
      "command": "npx",
      "args": ["-y", "mmnt-mcp-server"]
    }
  }
}

Additional notes

If you want to expose the server through a remote HTTP endpoint instead of running it locally, you would configure an HTTP MCP server entry with the appropriate URL. This particular setup uses a local stdio entry, which runs the package directly via npx and does not require a separate server URL.

Available tools

mmnt_search

Performs a search on the Mamont engine. Input: query (string) and page (number) to navigate results.

mmnt_cache

Retrieves a cached page by its unique id. Input: id (string) and onlyText (boolean) to return plain text.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
MMNT MCP Server - zbkm/mmnt-mcp-server | VeilStrat