Skip to main content
Glama

mong-mcp-server

A Model Context Protocol (MCP) server implementation that provides a moby-like random name generator ("mong") for use with tools like Claude Desktop and VS Code Copilot Agent.

Features

  • Exposes a moby-like random name generator through the MCP interface

  • Easy setup and configuration

Related MCP server: Elba MCP Server

Configuration for Claude Desktop

Add this server under the mcpServers key of Claude Desktop configuration. See the official document of the Model Context Protocol for details.

{
   "mcpServers": {
      "mong": {
         "command": "uvx",
         "args": [
            "--from",
            "git+https://github.com/toshihikoyanase/mong-mcp-server",
            "mong-mcp"
         ]
      }
   }
}

or

{
    "mcpServers": {
        "mong": {
            "command": "uv",
            "args": [
                "--directory",
                "/path/to/repository",
                "run",
                "python",
                "-m",
                "mong_mcp_server"
            ]
        }
    }
}

Configuration for VS Code Copilot Agent

Add this server under the servers key in your MCP configuration for VS Code. For example, to enable the MCP server in your workspace, create a .vscode/mcp.json file as follows:

{
    "servers": {
        "mong": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "--from",
                "git+https://github.com/toshihikoyanase/mong-mcp-server",
                "mong-mcp"
            ]
        }
    }
}

Install locally

  1. Clone the repository:

    git clone https://github.com/toshihikoyanase/mong-mcp-server.git
    cd mong-mcp-server
  2. Start the server:

    uv run python -m mong_mcp_server

Running Tests

Run the unit tests to verify the server functionality:

uv run python -m unittest discover tests/

License

This project is licensed under the MIT License. See the LICENSE file for details.

Available Tools

1 tool
get_random_nameB

Generate a random name like Docker does.

Inputs: no named parameters. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly distinct as it is the only one available, making disambiguation trivial.

    Naming Consistency5/5

    A single tool inherently has perfect naming consistency since there are no other tools to compare against. The name 'get_random_name' follows a clear verb_noun pattern, which is consistent with itself.

    Tool Count2/5

    A single tool is too few for a server named 'Mong MCP Server', which suggests a broader purpose or domain. This minimal toolset feels thin and underdeveloped, limiting the server's utility and scope.

    Completeness1/5

    The server is severely incomplete; with only one tool for generating random names, it lacks any meaningful coverage of a domain. There are obvious gaps as no other operations or resources are supported, making it inadequate for most agent tasks.

    Related MCP Connectors

    Related MCP Servers