Get the FREE Ultimate OpenClaw Setup Guide →

mcp s

A collection of MCP (Model Context Protocol) servers for AI assistants

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio masx200-mcp-servers python -m mcp-logistics \
  --env PYTHONUNBUFFERED="1"

How to use

This MCP server collection provides a set of agents to support multi-agent collaboration tasks. The Python-based servers (mcp-system-cleaner and mcp-logistics) offer domain-specific capabilities such as system maintenance automation and logistics information retrieval, while the TypeScript servers (mcp-file-manager and mcp-data-analyzer) provide file management operations and data analysis tooling. To run a server, choose the appropriate entry under mcp_config and start it with the specified command. Each server exposes its own interfaces (APIs or RPC endpoints) described in their respective READMEs, allowing AI agents to query status, perform actions, or request analyses. You can run multiple servers concurrently to compose a larger workflow where one server’s output feeds into another’s input.

How to install

Prerequisites:

  • Python 3.12 or later
  • Node.js 14 or later
  • git (optional, for cloning/readme updates)
  1. Clone the repository (if you haven't already): git clone <repository-url> cd <repository-root>

  2. Install and run Python servers:

    • Navigate to each Python server directory or ensure the package is installed in your Python environment.
    • Example (system-cleaner): python -m mcp-system-cleaner
    • Example (logistics): python -m mcp-logistics
    • Ensure dependencies are installed per server's README (usually via pip install -r requirements.txt).
  3. Install and run TypeScript servers:

    • Navigate to the TypeScript server directories and install dependencies: cd typescript/mcp-file-manager npm install

      Build if required by the project, e.g., npm run build

    • Start the server (the exact command may vary; the dist/server.js should be present after build): node dist/server.js
    • Repeat for mcp-data-analyzer in its directory.
  4. Validate operational status:

    • Check logs for startup messages indicating listening ports and endpoints.
    • Use curl or a client tool to ping each server endpoint as documented in their READMEs.
  5. Environment configuration (optional):

    • You can set environment variables per server (e.g., database URLs, API keys) as described in each server’s README.
    • Example for Python servers: PYTHONUNBUFFERED=1 to disable buffering in logs.

Note: This repository contains multiple independent MCP servers. You can start any combination of them to form your desired multi-agent workflow.

Additional notes

Tips and common issues:

  • Ensure you meet the runtime requirements for each server (Python 3.12+, Node.js 14+).
  • Some TypeScript servers may require a build step to generate dist/server.js; follow the individual server READMEs for build commands.
  • If an endpoint is not reachable, check firewall rules and port configuration; logs usually indicate port numbers and startup status.
  • Keep Python virtual environments isolated per server to avoid dependency conflicts.
  • If you update a server, rebuild TypeScript projects and reinstall Python requirements as needed.
  • The npm_package field is null for this collection since it comprises multiple non-packaged servers rather than a single npm package.

Related MCP Servers

Sponsor this space

Reach thousands of developers