x=hub

your toolset

    build deployment
    sign in

    forge-mcp

    mcpkey · package
    io.github.SalesforgeAI/forge-mcp · v1.0.0
    deploy just this

    MCP server for Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge

    run it

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

[Unit]
Description=MCP server forge (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/forge
WorkingDirectory=/var/lib/mcp/forge
ExecStart=/opt/mcp/my-agent/bin/forge.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/forge

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e SALESFORGE_API_KEY -e PRIMEFORGE_API_KEY -e LEADSFORGE_API_KEY -e INFRAFORGE_API_KEY -e MAILFORGE_API_KEY node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y @salesforge/[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-18T07:58:31+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:
  forge:
    image: node:22-alpine
    command:
    - sh
    - -c
    - npx -y supergateway@4 --stdio 'npx -y @salesforge/[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:
      SALESFORGE_API_KEY: ${SALESFORGE_API_KEY}
      PRIMEFORGE_API_KEY: ${PRIMEFORGE_API_KEY}
      LEADSFORGE_API_KEY: ${LEADSFORGE_API_KEY}
      INFRAFORGE_API_KEY: ${INFRAFORGE_API_KEY}
      MAILFORGE_API_KEY: ${MAILFORGE_API_KEY}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T07:58:31+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: forge
  namespace: mcp
  labels: &id001
    app: forge
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: forge
        image: node:22-alpine
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: SALESFORGE_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: SALESFORGE_API_KEY
        - name: PRIMEFORGE_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: PRIMEFORGE_API_KEY
        - name: LEADSFORGE_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: LEADSFORGE_API_KEY
        - name: INFRAFORGE_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: INFRAFORGE_API_KEY
        - name: MAILFORGE_API_KEY
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: MAILFORGE_API_KEY
        command:
        - sh
        - -c
        - npx -y supergateway@4 --stdio 'npx -y @salesforge/[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: forge
  namespace: mcp
spec:
  selector:
    app: forge
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T07:58:31+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:
  forge:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: forge
      image: node:22-alpine
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: SALESFORGE_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: SALESFORGE_API_KEY
      - name: PRIMEFORGE_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: PRIMEFORGE_API_KEY
      - name: LEADSFORGE_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: LEADSFORGE_API_KEY
      - name: INFRAFORGE_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: INFRAFORGE_API_KEY
      - name: MAILFORGE_API_KEY
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: MAILFORGE_API_KEY
      command:
      - sh
      - -c
      - npx -y supergateway@4 --stdio 'npx -y @salesforge/[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: SALESFORGE_API_KEY, PRIMEFORGE_API_KEY, LEADSFORGE_API_KEY, INFRAFORGE_API_KEY, MAILFORGE_API_KEY. 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 @salesforge/[email protected]
# env: SALESFORGE_API_KEY, PRIMEFORGE_API_KEY, LEADSFORGE_API_KEY, INFRAFORGE_API_KEY, MAILFORGE_API_KEY
    {
  "mcpServers": {
    "forge": {
      "command": "npx",
      "args": [
        "-y",
        "@salesforge/[email protected]"
      ],
      "env": {
        "SALESFORGE_API_KEY": "${SALESFORGE_API_KEY}",
        "PRIMEFORGE_API_KEY": "${PRIMEFORGE_API_KEY}",
        "LEADSFORGE_API_KEY": "${LEADSFORGE_API_KEY}",
        "INFRAFORGE_API_KEY": "${INFRAFORGE_API_KEY}",
        "MAILFORGE_API_KEY": "${MAILFORGE_API_KEY}"
      }
    }
  }
}
    #!/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 forge -e "SALESFORGE_API_KEY=${SALESFORGE_API_KEY}" -e "PRIMEFORGE_API_KEY=${PRIMEFORGE_API_KEY}" -e "LEADSFORGE_API_KEY=${LEADSFORGE_API_KEY}" -e "INFRAFORGE_API_KEY=${INFRAFORGE_API_KEY}" -e "MAILFORGE_API_KEY=${MAILFORGE_API_KEY}" -- npx -y @salesforge/[email protected]

    {
  "mcpServers": {
    "forge": {
      "command": "npx",
      "args": [
        "-y",
        "@salesforge/[email protected]"
      ],
      "env": {
        "SALESFORGE_API_KEY": "${SALESFORGE_API_KEY}",
        "PRIMEFORGE_API_KEY": "${PRIMEFORGE_API_KEY}",
        "LEADSFORGE_API_KEY": "${LEADSFORGE_API_KEY}",
        "INFRAFORGE_API_KEY": "${INFRAFORGE_API_KEY}",
        "MAILFORGE_API_KEY": "${MAILFORGE_API_KEY}"
      }
    }
  }
}
    {
  "servers": {
    "forge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@salesforge/[email protected]"
      ],
      "env": {
        "SALESFORGE_API_KEY": "${SALESFORGE_API_KEY}",
        "PRIMEFORGE_API_KEY": "${PRIMEFORGE_API_KEY}",
        "LEADSFORGE_API_KEY": "${LEADSFORGE_API_KEY}",
        "INFRAFORGE_API_KEY": "${INFRAFORGE_API_KEY}",
        "MAILFORGE_API_KEY": "${MAILFORGE_API_KEY}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.SalesforgeAI/forge-mcp
    • 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.