More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    start mcp gateway

    1

    Installs the MCP gateway and connects a client to an MCP server you already run

    Free

    1 useSecurity scanned
    start mcp gateway

    start mcp gateway

    Example session with this skill installed

    Set up an MCP gateway for my server running at http://127.0.0.1:8080/mcp. Use the namespace 'dev-tools' and no login is required. I'm using Claude Desktop.

    • Read your context and instructions
    • Compiled the start mcp gateway

    I cloned the gateway repository, configured Docker, and started Redis and the gateway. The gateway is routing to your server, and Claude Desktop is pointed at the gateway URL.

    MCP Gateway deployment summary

    ComponentStatusDetail
    RepositoryCloned$HOME/mcp-server-gateway
    RedisRunningHealthy
    GatewayRunningHealthy on port 8090
    Namespacedev-toolsRegistered
    UpstreamYour serverhttp://127.0.0.1:8080/mcp
    LoginOffOpen namespace
    CheckPassedHealth ok, tools/list succeeded

    Gateway configuration

    The gateway container reaches your server at http://host.docker.internal:8080/mcp. Claude Desktop does not use port 8080. It uses the gateway:

    http://localhost:8090/dev-tools/mcp

    {
      "mcpServers": {
        "dev-tools": {
          "type": "http",
          "url": "http://localhost:8090/dev-tools/mcp"
        }
      }
    }
    

    Next step

    Restart Claude Desktop and reload MCP servers. Ask it to list the tools on dev-tools. No gateway login is required for this namespace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    An MCP server on your laptop is not something Claude, Cursor, or Copilot can share safely. Each client wants its own connection, and there is no single front door, health check, or place to turn login on later.

    This skill installs the MCP gateway and points it at the server you already run. Your agent clones the public gateway repository if it is not on the machine, starts Redis and the gateway in Docker, and registers your server under a namespace you choose. Clients then use one address:

    http://localhost:8090/<namespace>/mcp

    You keep running your own MCP server. The skill does not replace it. It gives every agent the same URL, checks that the gateway is healthy, and confirms the server answers through that URL. Login stays off unless you ask for it. You supply any OAuth client id or secret yourself. Nothing in the skill is a credential or a certificate.

    Use it when you want Claude Desktop, Claude Code, Cursor, Copilot, or another MCP client to reach a local server without giving each one a different port and config.

    Requires Docker and Docker Compose. Upstream servers must be reachable from the gateway container. Node.js is needed for automated connectivity testing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    • Free with an Agensi account

    Requires

    GitHub
    Docker
    Docker Compose
    Git
    An You Already Run MCP
    Gateway MCP
    Attached Config MCP
    Remote Runner MCP
    Remote MCP

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    Allowed Hosts

    github.com
    docker.com

    File Scopes

    mcp-gateway/.env
    mcp-gateway/configs/attached-mcp-config.yml
    mcp-gateway/attached-gateway.yml
    mcp-gateway/certs/**

    The skill clones the public gateway repository, writes a local encryption key, and registers the buyer’s existing MCP server. It starts Redis and the gateway in Docker. It does not read credentials from other projects.

    Listed29 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the complex setup of the Harish Gaggar MCP gateway, handling Docker networking, Redis configuration, and encryption key generation that usually requires manual command-line expertise.

    Yes, the skill is designed to route traffic from any MCP-compliant client, including Cursor, Claude Desktop, and other IDEs, by providing a unified localhost endpoint.

    The host machine must have Docker, Docker Compose, and Node.js installed and running to successfully build the containers and validate the connection.

    The skill automates the mapping of `host.docker.internal` and the creation of the `attached-mcp-config.yml`, ensuring your Docker containers can talk to services running natively on your machine.

    You receive the automated deployment workflow, environment configuration scripts, and the validation utility to ensure your gateway and upstream servers are communicating correctly.

    New in LLM Ops