x=hub

your toolset

    build deployment
    sign in

    open-mcp-apps

    mcpkey · package
    io.github.2nd1st/open-mcp-apps · v0.5.9
    deploy just this

    Persistent, interactive MCP Apps — the AI builds an app once, you both reuse it

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    #!/usr/bin/env bash
# open-mcp-apps (io.github.2nd1st/open-mcp-apps), recipe baremetal (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-open-mcp-apps.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec npx -y supergateway@4 --stdio 'npx -y @2nd1st/[email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz

[Unit]
Description=MCP server open-mcp-apps (toolset my-agent), generated by Hub
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=mcp
Group=mcp
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/open-mcp-apps
WorkingDirectory=/var/lib/mcp/open-mcp-apps
ExecStart=/opt/mcp/my-agent/bin/open-mcp-apps.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/open-mcp-apps

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e OMA_DB -e OMA_VIEWER -e OMA_DYNAMIC_TOOLS node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y @2nd1st/[email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-17T23:56:03+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
#   cp .env.example .env    # fill the ${VAR}s
#   docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
  open-mcp-apps:
    image: node:22-alpine
    command:
    - sh
    - -c
    - npx -y supergateway@4 --stdio 'npx -y @2nd1st/[email protected]' --outputTransport streamableHttp
      --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
    ports:
    - 127.0.0.1:8101:8000
    volumes:
    - npm-cache:/root/.npm
    healthcheck:
      test:
      - CMD-SHELL
      - wget -qO- http://127.0.0.1:8000/healthz || exit 1
      interval: 30s
      timeout: 5s
      retries: 5
      start_period: 2m
    restart: unless-stopped
    environment:
      OMA_DB: ${OMA_DB}
      OMA_VIEWER: ${OMA_VIEWER}
      OMA_DYNAMIC_TOOLS: ${OMA_DYNAMIC_TOOLS}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-17T23:56:03+00:00).
#   kubectl create namespace mcp
#   kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
#   kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
  name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: open-mcp-apps
  namespace: mcp
  labels: &id001
    app: open-mcp-apps
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: open-mcp-apps
        image: node:22-alpine
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: OMA_DB
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: OMA_DB
        - name: OMA_VIEWER
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: OMA_VIEWER
        - name: OMA_DYNAMIC_TOOLS
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: OMA_DYNAMIC_TOOLS
        command:
        - sh
        - -c
        - npx -y supergateway@4 --stdio 'npx -y @2nd1st/[email protected]' --outputTransport streamableHttp
          --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
        readinessProbe:
          httpGet:
            path: /healthz
            port: http
          initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
  name: open-mcp-apps
  namespace: mcp
spec:
  selector:
    app: open-mcp-apps
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-17T23:56:03+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
  open-mcp-apps:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: open-mcp-apps
      image: node:22-alpine
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: OMA_DB
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: OMA_DB
      - name: OMA_VIEWER
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: OMA_VIEWER
      - name: OMA_DYNAMIC_TOOLS
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: OMA_DYNAMIC_TOOLS
      command:
      - sh
      - -c
      - npx -y supergateway@4 --stdio 'npx -y @2nd1st/[email protected]' --outputTransport streamableHttp
        --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
      readinessProbe:
        httpGet:
          path: /healthz
          port: http
        initialDelaySeconds: 10

# helm install my-agent helm/my-agent -n mcp

    in the cloud

    one click: the provider's deploy form opens filled in, in your own account
    koyeb
    deploy to koyeb

    The form opens with CHANGE_ME for each value you supply: OMA_DB, OMA_VIEWER, OMA_DYNAMIC_TOOLS. Fill them in before you deploy.

    Clients connect to the service's https://…koyeb.app address plus /mcp.

    azure
    deploy to azuretemplate

    A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.

    connect to it

    copy what your client needs
    npx -y @2nd1st/[email protected]
# env: OMA_DB, OMA_VIEWER, OMA_DYNAMIC_TOOLS
    {
  "mcpServers": {
    "open-mcp-apps": {
      "command": "npx",
      "args": [
        "-y",
        "@2nd1st/[email protected]"
      ],
      "env": {
        "OMA_DB": "${OMA_DB}",
        "OMA_VIEWER": "${OMA_VIEWER}",
        "OMA_DYNAMIC_TOOLS": "${OMA_DYNAMIC_TOOLS}"
      }
    }
  }
}
    #!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add open-mcp-apps -e "OMA_DB=${OMA_DB}" -e "OMA_VIEWER=${OMA_VIEWER}" -e "OMA_DYNAMIC_TOOLS=${OMA_DYNAMIC_TOOLS}" -- npx -y @2nd1st/[email protected]

    {
  "mcpServers": {
    "open-mcp-apps": {
      "command": "npx",
      "args": [
        "-y",
        "@2nd1st/[email protected]"
      ],
      "env": {
        "OMA_DB": "${OMA_DB}",
        "OMA_VIEWER": "${OMA_VIEWER}",
        "OMA_DYNAMIC_TOOLS": "${OMA_DYNAMIC_TOOLS}"
      }
    }
  }
}
    {
  "servers": {
    "open-mcp-apps": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@2nd1st/[email protected]"
      ],
      "env": {
        "OMA_DB": "${OMA_DB}",
        "OMA_VIEWER": "${OMA_VIEWER}",
        "OMA_DYNAMIC_TOOLS": "${OMA_DYNAMIC_TOOLS}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.2nd1st/open-mcp-apps
    • not probed yet: tools unpinned, ingest lists them

    tools

    Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.