Skip to main content
Glama
deenesjakoruzh
gbastkowski

mcp-proxy

by gbastkowski
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

mcp-akiko-proxy

MCP stdio proxy over SSH, exposing remote MCP servers (bound to localhost on a remote machine) as tools on the local machine.

Establishes SSH tunnels using your existing ~/.ssh/config host alias, connects to the remote MCP servers over streamable-http through the tunnel, and exposes their tools aggregated behind one local stdio MCP server.

Default targets (configurable):

name

local port

remote url

exposes

blender

8001

http://127.0.0.1:8001/

Blender MCP (blender-mcp daemon on the remote)

qgis

8000

http://127.0.0.1:8000/mcp

QGIS MCP (qgis-mcp daemon on the remote)

Graceful degradation

If the tunnel is down or a backend is unreachable, that backend's tools vanish from tools/list (or their calls return a clear error). The proxy keeps running and retries periodically — it never crashes because a backend is missing.

Related MCP server: ssh-chat-mcp

Usage

# run (stdio; opencode/claude/any MCP client will spawn it):
npx -y github:gbastkowski/mcp-proxy
# or clone + npm install + npm start

Configuration (env vars)

var

default

purpose

MCP_PROXY_HOST

akiko

ssh host alias from ~/.ssh/config

MCP_PROXY_TUNNELS

blender+qgis defaults

JSON [{ name, localPort, remotePort, url }]

MCP_PROXY_TUNNEL_RETRY_MS

15000

reconnect/retry interval for dead backends

MCP_PROXY_CONNECT_TIMEOUT_MS

10000

wait for a tunnel/backend port

MCP_PROXY_SSH_TIMEOUT_MS

5000

ssh ConnectTimeout

MCP_PROXY_NO_TUNNEL

unset

truthy: skip ssh, talk to localhost directly (testing)

Example: opencode on a Macbook using Blender+QGIS on the akiko box

{
  "mcp": {
    "akiko": {
      "type": "local",
      "command": ["npx", "-y", "github:gbastkowski/mcp-proxy"]
    }
  }
}

Run MCP_PROXY_HOST=akiko npx -y github:gbastkowski/mcp-proxy — the host is read from your normal ssh config, keys from your agent.

Requirements

  • Node >= 18

  • ssh with a configured host alias for the remote machine + working key auth

  • On the remote: the target MCP servers bound to 127.0.0.1 (they are not exposed to the network; the SSH tunnel is the only bridge)

License

MIT

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • Docker MCP

    Isak-Landin
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables remote Docker management over SSH via a local MCP server, providing tools to manage containers, images, Compose, and system resources.
    1
    GPL 3.0

  • ssh-chat-mcp

    aiplatforms-ru
    A
    license
    A
    quality
    D
    maintenance
    Zero-config SSH/SFTP MCP server that lets an LLM client open temporary SSH/SFTP sessions to remote hosts, run commands, and upload/download files without holding any pre-baked credentials.
    17
    6 npm
    2
    MIT

  • Bonsai MCP

    Show2Instruct
    A
    license
    A
    quality
    B
    maintenance
    Connects MCP clients to a local Blender + Bonsai (BlenderBIM) session for scene inspection, IFC project querying, viewport screenshots, and executing Python code in Blender.
    8
    6
    MIT

  • AI Ops MCP

    Finn-Aigc
    A
    license
    Not graded
    quality
    B
    maintenance
    Local SSH credential broker and stdio MCP server that enables AI clients to perform SSH and SFTP operations via stable server_id aliases without exposing passwords, private keys, or passphrases.
    0
    1
    MIT