semvec/pypi-packages huggingface dataset:
mingday-linux-mcp-server 0.1.2.dev0
MCP server for read-only Linux system administration, diagnostics, and troubleshooting
Requires Python: >=3.10

<!-- mcp-name: io.github.rhel-lightspeed/linux-mcp-server -->
[![CI](https://github.com/rhel-lightspeed/linux-mcp-server/actions/workflows/ci.yml/badge.svg)](https://github.com/rhel-lightspeed/linux-mcp-server/actions/workflows/ci.yml)
[![Coverage](https://codecov.io/gh/rhel-lightspeed/linux-mcp-server/graph/badge.svg?token=TtUkG1y0rx)](https://codecov.io/gh/rhel-lightspeed/linux-mcp-server)
[![PyPI](https://img.shields.io/pypi/v/linux-mcp-server?label=PyPI)](https://pypi.org/project/linux-mcp-server)
[![Docs](https://img.shields.io/badge/Docs-Linux%20MCP%20Server-red)](https://rhel-lightspeed.github.io/linux-mcp-server/)


# Linux MCP Server

A Model Context Protocol (MCP) server for read-only Linux system administration, diagnostics, and troubleshooting on RHEL-based systems.


## Features

- **Read-Only Operations**: All tools are strictly read-only for safe diagnostics
- **Remote SSH Execution**: Execute commands on remote systems via SSH with key-based authentication
- **Multi-Host Management**: Connect to different remote hosts in the same session
- **Comprehensive Diagnostics**: System info, services, processes, logs, network, and storage
- **Configurable Log Access**: Control which log files can be accessed via environment variables
- **RHEL/systemd Focused**: Optimized for Red Hat Enterprise Linux systems


## Installation and Usage

For detailed instructions on setting up and using the Linux MCP Server, please refer to our official documentation:

- **[Installation Guide]**: Detailed steps for `pip`, `uv`, and container-based deployments.
- **[Usage Guide]**: Information on running the server, configuring LLM clients, and troubleshooting.
- **[Cheatsheet]**: A reference for what prompts to use to invoke various tools.


[Installation Guide]: https://rhel-lightspeed.github.io/linux-mcp-server/install/
[Usage Guide]: https://rhel-lightspeed.github.io/linux-mcp-server/usage/
[Cheatsheet]: https://rhel-lightspeed.github.io/linux-mcp-server/cheatsheet/
iflow-mcp_smartaec-ifcmcp 0.1.0
An MCP server that enables LLM agents to talk with IFC (Industry Foundation Classes) files
Requires Python: >=3.11

# ifcMCP
An MCP server that enables LLM agents to talk with IFC (Industry Foundation Classes) files

## Star History

[![Star History Chart](https://api.star-history.com/svg?repos=smartaec/ifcMCP&type=Date)](https://www.star-history.com/#smartaec/ifcMCP&Date)

# related packages
1. ifcopenshell
2. FastMCP

# supported tools
1. get_entities
2. get_named_property_of_entities
3. get_entity_properties
4. get_entity_location
5. get_entities_in_spatial
6. get_openings_on_wall
7. get_space_boundaries

# how to use it
1. clone this repo
2. install packages needed: [ifcopenshell](https://docs.ifcopenshell.org/ifcopenshell-python/installation.html), FastMCP
3. start command line interface in folder `ifcMCP`, and run the command `python server.py`
4. open your favorite LLM tools and setup MCP server with the following configuration:
```
{
  "mcpServers": {
    "ifcMCP-server": {
      "name": "ifcMCP",
      "type": "streamableHttp",
      "description": "A simple MCP server to handle ifc files",
      "isActive": true,
      "tags": [],
      "baseUrl": "http://127.0.0.1:8000/mcp"
    }
  }
}
```
![basic_demo](250608_ifcMCP_demo-en.gif)

# contributors
Jia-Rui Lin (lin611#tsinghua.edu.cn)

Department of Civil Engineering, Tsinghua University

Key Laboratory of Digital Construction and Digital Twin led by Prof. Peng Pan

# cite us
```
@article{JRLin2506,
	author = {Jia-Rui Lin and Peng Pan},
	title = {ifcMCP: Enabling LLM agents to talk with IFC files},
	year = {2025}
}
```
env-diff-cli 0.1.0
Compare two .env files — show added, removed, and changed keys without leaking values
Requires Python: >=3.9
Keywords: cli, devtools, diff, dotenv, env

# env-diff

Compare two `.env` files — see what's added, removed, or changed **without leaking secret values**.

## Install

```bash
pip install env-diff
```

## Usage

```bash
env-diff .env.example .env.local
```

```
Added (2)
  + NEW_API_KEY
  + FEATURE_FLAG

Removed (1)
  - OLD_SECRET

Changed (1)
  ~ DATABASE_URL

3 difference(s) found
```

### Options

| Flag | Description |
|------|-------------|
| `--show-values` | Show masked values for changed keys (e.g. `sk****yz`) |
| `--no-color` | Disable colored output |
| `-q, --quiet` | Exit code only: `0` = identical, `1` = different |

## Exit Codes

- `0` — files are identical
- `1` — differences found
- `2` — file not found or error

## Why?

Every dev has done `diff .env.example .env` and accidentally pasted the output somewhere public. `env-diff` shows you **what changed** without showing **the actual secrets**.

Perfect for:
- PR reviews ("which env vars changed?")
- Deployment checklists
- Onboarding ("what do I need to add to my .env?")
- CI checks (compare `.env.example` against required vars)

## License

MIT