Is Suckless Mcp safe to use?

Suckless Mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install Suckless Mcp?

Suckless Mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.

What can Suckless Mcp do?

Suckless Mcp provides 5 tools: Install, Uninstall, Commands, Configuration, Philosophy. See the full tools list on the server page for descriptions and parameters.

What AI clients work with Suckless Mcp?

Suckless Mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.

Is Suckless Mcp actively maintained?

Suckless Mcp is actively maintained — last commit was 28 days ago. It has 1 GitHub stars.

Suckless Mcp

Name: Suckless Mcp
Author: roverbird

by roverbird

suckless-mcp is a RUST MCP gateway that runs behind Caddy and turns your agentic CLI scripts into MCP tools. One binary, two config files, and a dir of cli skills. No framework, no bloat.

1 5 tools GitHub

No known CVEs

MIT license

Actively maintained

Last commit 28d ago

Works with most clients

Transport: stdio, http

5 tools

Grade F

Edit this pageView history

DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "suckless-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/suckless-mcp)](https://mcppedia.org/s/suckless-mcp)

Read me

What Suckless Mcp does

The suckless MCP gateway. Turn any CLI tool into an MCP endpoint.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

37/100across 5 weighted dimensions

How we score →

0255075100

−63

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Inventory

Tools (5)

Click any tool to inspect its schema.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Suckless Mcp safe to use?: Suckless Mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install Suckless Mcp?: Suckless Mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What can Suckless Mcp do?: Suckless Mcp provides 5 tools: Install, Uninstall, Commands, Configuration, Philosophy. See the full tools list on the server page for descriptions and parameters.
What AI clients work with Suckless Mcp?: Suckless Mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is Suckless Mcp actively maintained?: Suckless Mcp is actively maintained — last commit was 28 days ago. It has 1 GitHub stars.

Similar servers

Others in devops

View all →

Mcp Gitlab96

MCP server for using the GitLab API

1.7k 12

Mcp Router92

A Unified MCP Server Management App (MCP Manager).

2.1k 2

Komodo MCP Server91

MCP server for Komodo - manage Docker containers, servers, stacks, and deployments via AI

9 11

Mcp Nixos90

MCP-NixOS - Model Context Protocol Server for NixOS resources

730 2

MCP Security Weekly

Get CVE alerts and security updates for Suckless Mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

DevOps

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "suckless-mcp": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/suckless-mcp)](https://mcppedia.org/s/suckless-mcp)

Read me

What Suckless Mcp does

The suckless MCP gateway. Turn any CLI tool into an MCP endpoint.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

suckless-mcp

The suckless MCP gateway. Turn any CLI tool into an MCP endpoint.

One binary. One config file. One key file. One dir of skills. Same --flags everywhere.

Install

Via cargo (for Rust developers)

cargo install suckless-mcp

Quick Install (Linux x86_64)

# Install with one command
curl -fsSL https://raw.githubusercontent.com/roverbird/suckless-mcp/main/install.sh -o install.sh
chmod +x install.sh
./install.sh

# Check status
suckless-mcp --status

The installer does everything:

Downloads the pre-compiled binary from GitHub Releases
Copies skills from the repository to /opt/skills
Creates /etc/suckless-mcp/config.toml with defaults
Generates an API key in /etc/suckless-mcp/keys.toml
Creates a suckless system user
Installs a systemd service (auto-start on boot)

Manual Installation

# Copy binary
cp suckless-mcp /usr/local/bin/

# Create config
mkdir -p /etc/suckless-mcp
cat > /etc/suckless-mcp/config.toml << EOF
listen_host = "127.0.0.1"
listen_port = 8080
max_concurrent_tools = 5
EOF

# Add a skill
mkdir -p /opt/skills/weather
cat > /opt/skills/weather/skill.toml << EOF
name = "weather"
description = "Get weather forecast for a city"
public = false   # true = no auth required

[runtime]
entrypoint = "weather.py"
timeout_secs = 30

[inputs.city]
type = "string"
flag = "--city"
required = true
description = "City name"
EOF

# Add your CLI tool
cp weather.py /opt/skills/weather/

# Add an API key
suckless-mcp --keys-add --id admin --key "your-secret-key"

# Run
suckless-mcp --serve

Uninstall

./install.sh --uninstall

What is this?

suckless-mcp is a gateway that exposes your existing CLI tools as MCP endpoints.

AI agents connect to suckless-mcp over HTTP
suckless-mcp reads skill.toml to understand your tool
suckless-mcp calls your CLI tool with --flags
Your tool outputs JSON back to the AI

AI Agent → Caddy → suckless-mcp → your CLI tool (--flags)
                ← suckless-mcp ← JSON output

Why?

Problem	Solution
MCP SDK requires rewriting tools	Keep your tools, add skill.toml
Need authentication	Built into gateway
Each tool needs its own server	One gateway, many tools
Setup complexity	One binary, two configs

What you need

suckless-mcp binary (this)
config.toml - host, port, concurrency limits
keys.toml - API keys (managed via CLI)
/opt/skills/ - one subfolder per tool
skill.toml - describes your tool to AI
Your CLI tool - must use --flags and output JSON

Authentication: Per-tool, not all-or-nothing

suckless-mcp supports mixed auth on a single endpoint:

Tool type	`public` flag	`tools/list` visibility	Can be called without auth
Public	`true`	Visible to everyone	✓ Yes
Private	`false` (default)	Only visible to authenticated clients	✗ No (returns 401)

# Public tool example (weather data, public API)
name = "weather"
public = true

# Private tool example (database query)
name = "db_query"
public = false   # or omit the field entirely

This gives you:

One endpoint (/mcp) for both public and private tools
Clean discovery - agents only see tools they can actually call
No complex OAuth - simple Bearer tokens for private tools

How a skill folder looks

/opt/skills/weather/
├── skill.toml      # Machine-readable manifest
└── weather.py      # Your CLI tool

The contract: Your CLI tool MUST

Use --flags only - no positional args, no shell string concatenation
Output valid JSON - nothing else to stdout
Exit 0 on success, 1 on error

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

37/100across 5 weighted dimensions

How we score →

0255075100

−63

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Inventory

Tools (5)

Click any tool to inspect its schema.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Suckless Mcp safe to use?: Suckless Mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install Suckless Mcp?: Suckless Mcp can be installed by cloning its GitHub repository and following the setup instructions in the README.
What can Suckless Mcp do?: Suckless Mcp provides 5 tools: Install, Uninstall, Commands, Configuration, Philosophy. See the full tools list on the server page for descriptions and parameters.
What AI clients work with Suckless Mcp?: Suckless Mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is Suckless Mcp actively maintained?: Suckless Mcp is actively maintained — last commit was 28 days ago. It has 1 GitHub stars.