Skip to content

Month: May 2026

Supergateway: Makes Self-Hosting MCP Servers Much Easier

I recently came across Supergateway and it solved a problem I was running into with MCP servers.

I was looking for a cleaner way to work with multiple MCP servers without having to install a ton of separate services, keep random background processes running, or execute npx commands all over the server every time I wanted to expose a tool. Supergateway acts as a bridge between stdio-based MCP servers and transports like SSE, WebSockets, and Streamable HTTP, which made things much easier to centralize and manage.

What I found especially useful was being able to take existing MCP servers that normally only run locally over stdio and expose them in a more flexible way for remote access, containers, or shared environments. It simplified the overall setup and made my MCP environment feel a lot more organized instead of having dozens of individually managed processes everywhere.

It also seems to be becoming a pretty common approach in the MCP ecosystem for bridging transports and simplifying deployments, especially in Docker and self-hosted environments.

https://github.com/supercorp-ai/supergateway

Example

 mcp-openweathermap:
    image: supercorp/supergateway:latest
    container_name: mcp-openweathermap
    command: >
        --stdio "npx -y @tristau/openweathermap-mcp --apikey myKey"
        --port 8000
        --outputTransport sse
    ports:
      - 8000:8000        
    restart: unless-stopped
1 Comment

playwright/mcp localhost error

I kept running into a playwright/mcp localhost access issue when trying to connect to the container from outside Docker. By default, the service only allowed connections to localhost:8931, which prevented external access from the host machine or other containers.

After a lot of troubleshooting, this Docker Compose configuration resolved the issue and allowed external connections successfully.

Notes

  • This example uses Chromium in headless mode.
  • Port 8931 is exposed to the host machine.
  • PLAYWRIGHT_MCP_NO_SANDBOX=true can help in certain containerized environments.
  • For production deployments, consider restricting --allowed-hosts instead of using "*".
  mcp-playwright:
    image: mcr.microsoft.com/playwright/mcp
    container_name: mcp-playwright
    entrypoint: ["node", "/app/cli.js"]
    command: 
      - "--host"
      - "0.0.0.0"
      - "--port"
      - "8931"
      - "--allowed-hosts"
      - "*"  # Allows connections from your host machine
      - "--browser"
      - "chromium"
      - "--headless"
    environment:
      - PLAYWRIGHT_MCP_NO_SANDBOX=true
    ports:
      - "8931:8931"
    restart: unless-stopped
Leave a Comment

IPs for Monitoring

Before I lose this list and this post again.

10 to 20 safe high performance IP addresses that can be pinged for monitoring?
byu/ylluminate insysadmin

  • Lumen / Level 3 / Verizon: 4.2.2.2
  • Lumen / Level 3 / Verizon: 4.2.2.3
  • Lumen / Level 3 / Verizon: 4.2.2.4
  • Lumen / Level 3 / Verizon: 4.2.2.5
  • Lumen / Level 3 / Verizon: 4.2.2.6
  • Lumen / Level 3 / Verizon – California: 209.244.0.3
  • UltraDNS: 64.6.64.6 (2620:74:1b::1:1)
  • UltraDNS: 64.6.65.6 (2620:74:1c::2:2)
  • UltraDNS Virginia: 156.154.70.1
  • Dotcom-Monitor/Dallas: 69.162.81.155 (2607:ff68:105::3)
  • Dotcom-Monitor/Denver: 192.199.248.75 (2607:fc88:100:2b::2)
  • Dotcom-Monitor/Miami: 162.254.206.227 (2604:bc80:8001:1064::2)
  • Dotcom-Monitor/Chicago: 209.142.68.29 (2602:fea7:d00::25)
  • Dotcom-Monitor/Minneapolis: 207.250.234.100 (2001:4870:200e:100::2)
  • Dotcom-Monitor/Montreal: 184.107.126.165
  • Dotcom-Monitor/New York: 206.71.50.230 (2604:eb80:1:6::10)
  • Dotcom-Monitor/San Francisco: 65.49.22.66 (2001:470:1:1ab::2)
  • Dotcom-Monitor/Seattle: 23.81.0.59 (2607:f5b2:1:a00b:5::2)
  • Dotcom-Monitor/Washington DC: 207.228.238.7 (2605:4a00:121:f003::2)
  • Google DNS: 8.8.8.8
  • Google DNS: 8.8.4.4
  • Cisco Umbrella/OpenDNS (anycast routing): 208.67.222.222
  • Cisco Umbrella/OpenDNS (anycast routing): 208.67.220.220
  • CloudFlare: 1.1.1.1
  • CloudFlare: 1.0.0.1
  • Norton Connectsafe: 198.153.192.1
  • Norton Connectsafe: 198.153.194.2
  • DNSResolvers.com: 205.210.42.205
  • DNSResolvers.com: 64.68.200.200
  • Quad9: 9.9.9.9 (2620:fe::9)
  • Quad9: 149.112.112.112 (2620:fe::fe)
Leave a Comment