Labsco
MCP SERVER

Claude.ai MCP Server (Self-hosted)

by LeszczynskiKarol

A self-hosted connector that runs AWS CLI commands with your local profile, so the credentials never leave your machine.

Editors, Terminals & Local Dev Environment
Summary
Your infrastructure, reached from a chat, with the keys still on your desk.

A Claude.ai custom connector needs a public HTTPS endpoint and your AWS profile does not have one; the frp tunnel bridges that without copying credentials anywhere. The cost is genuine setup, a VPS and a certificate, before the first command runs.

What it is

A small Node MCP server you run on your own machine and add to Claude.ai as a custom connector through your own tunnel. It runs AWS CLI commands against your local profile, and its other tools reach SSH, the local shell and filesystem, the GitHub REST API, PostgreSQL over SSH and PM2 on remote hosts.

What you get
  • AWS CLI commands executed with your local profile (aws_cli)
  • SSH into your own servers using your .pem keys
  • Shell commands run on the local machine, and files written directly to local disk in full Unicode with no shell quoting
  • PostgreSQL queries against remote hosts reached over SSH, and PM2 process inspection on those hosts
  • The GitHub REST API called with your personal access token
  • Iteration over documents longer than the context window
  • Credentials stay local: the tunnel carries MCP requests and their results, not your keys
Requirements

A recent Node, plus the tunnel it is built around: nginx with a certificate and frps on a VPS, and frpc on the machine that holds your credentials.