mpop

io.github.meshpopPublished by GitHub account meshpopv4.9.0Updated Oct 24, 2026

Server fleet management MCP — monitor, deploy, and manage distributed Linux servers

VerifiedSTDIODesktop onlyCloud & Infrastructure

Server details

Identifier: io.github.meshpop/mpop
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account meshpop for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.meshpop%2Fmpop.svg)](https://sourceweft.com/mcp/io.github.meshpop%2Fmpop?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server for fleet management of distributed Linux servers, letting an assistant monitor, deploy to, and manage them.

What you can do: Monitor distributed Linux servers in a fleet, per the registry description of server fleet management capabilities. Deploy to managed servers. Manage the fleet's servers. No tool list, instructions or README is supplied, so the exact operations and their scope cannot be confirmed.
When to use it: Consider it when an assistant should help operate a fleet of distributed Linux servers, for example to check their state, roll out deployments, or carry out management tasks from a single MCP connection.
Requirements: Runs as a local process on the user's machine over stdio and is marked desktop only. No packages, environment variables, headers or authentication are declared, so how it reaches the managed servers and what credentials it needs are not stated.

Before you install

Deploy and management actions can change or disrupt production Linux servers. The input does not document which credentials it uses, what it writes or deletes, or what data leaves the machine; review these before connecting it to real infrastructure.

Installation

In SourceWeft

Open mpop in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v4.9.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.