x=hub

your toolset

    build deployment
    sign in

    SEO Tools: Yandex.Webmaster

    mcpkey · package
    io.github.antohins/seo-tools-mcp-ywm · v1.8.0
    deploy just this

    MCP server for Yandex.Webmaster search queries (read-only).

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    # once, as root:
    # as_mcp DIR COMMAND...: runs COMMAND as the mcp user in DIR, its home, sandboxed as the
    # units are: a package's install scripts can write to DIR only, as the server later can
    as_mcp() {
      local dir="$1"; shift
      systemd-run --quiet --wait --pipe --collect --uid=mcp --gid=mcp \
        -p WorkingDirectory="$dir" -p Environment=HOME="$dir" -p ReadWritePaths="$dir" \
        -p NoNewPrivileges=true -p ProtectSystem=strict -p ProtectHome=true -p PrivateTmp=true \
        -- "$@" </dev/null
    }
    install -d -m 0750 -o mcp -g mcp /var/lib/mcp/seo-tools-mcp-ywm
    # seo-tools-mcp-ywm: its packages, installed whole before its unit starts (no session installs)
    # npx takes a half-installed tree for installed: a rerun starts them afresh
    systemctl stop mcp-my-agent-seo-tools-mcp-ywm.service 2>/dev/null || true
    as_mcp /var/lib/mcp/seo-tools-mcp-ywm rm -rf /var/lib/mcp/seo-tools-mcp-ywm/.npm/_npx
    as_mcp /var/lib/mcp/seo-tools-mcp-ywm npx --yes [email protected] -- true
    as_mcp /var/lib/mcp/seo-tools-mcp-ywm npx --yes --package=supergateway@4 -- true
    
    #!/usr/bin/env bash
    # seo-tools-mcp-ywm (io.github.antohins/seo-tools-mcp-ywm), recipe baremetal (generated).
    # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-seo-tools-mcp-ywm.service.
    set -euo pipefail
    export HOST=127.0.0.1 PORT=8101
    exec npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz
    
    [Unit]
    Description=MCP server seo-tools-mcp-ywm (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/seo-tools-mcp-ywm
    WorkingDirectory=/var/lib/mcp/seo-tools-mcp-ywm
    ExecStart=/opt/mcp/my-agent/bin/seo-tools-mcp-ywm.sh
    Restart=on-failure
    RestartSec=5
    NoNewPrivileges=true
    ProtectSystem=strict
    ProtectHome=true
    PrivateTmp=true
    ReadWritePaths=/var/lib/mcp/seo-tools-mcp-ywm
    
    [Install]
    WantedBy=multi-user.target
    
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e YANDEX_OAUTH_TOKEN -e YWM_OAUTH_TOKEN -e YANDEX_CLIENT_ID -e YANDEX_CLIENT_SECRET -e YWM_HOST_ID -e YWM_USER_ID node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y [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-18T22:14:08+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:
      seo-tools-mcp-ywm:
        image: node:22-alpine
        command:
        - sh
        - -c
        - npx -y supergateway@4 --stdio 'npx -y [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:
          YANDEX_OAUTH_TOKEN: ${YANDEX_OAUTH_TOKEN}
          YWM_OAUTH_TOKEN: ${YWM_OAUTH_TOKEN}
          YANDEX_CLIENT_ID: ${YANDEX_CLIENT_ID}
          YANDEX_CLIENT_SECRET: ${YANDEX_CLIENT_SECRET}
          YWM_HOST_ID: ${YWM_HOST_ID}
          YWM_USER_ID: ${YWM_USER_ID}
    volumes:
      npm-cache: {}
      uv-cache: {}
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T22:14:08+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: seo-tools-mcp-ywm
      namespace: mcp
      labels: &id001
        app: seo-tools-mcp-ywm
    spec:
      replicas: 1
      selector:
        matchLabels: *id001
      template:
        metadata:
          labels: *id001
        spec:
          containers:
          - name: seo-tools-mcp-ywm
            image: node:22-alpine
            ports:
            - containerPort: 8000
              name: http
            env:
            - name: YANDEX_OAUTH_TOKEN
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: YANDEX_OAUTH_TOKEN
            - name: YWM_OAUTH_TOKEN
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: YWM_OAUTH_TOKEN
            - name: YANDEX_CLIENT_ID
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: YANDEX_CLIENT_ID
            - name: YANDEX_CLIENT_SECRET
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: YANDEX_CLIENT_SECRET
            - name: YWM_HOST_ID
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: YWM_HOST_ID
            - name: YWM_USER_ID
              valueFrom:
                secretKeyRef:
                  name: mcp-credentials
                  key: YWM_USER_ID
            args:
            - sh
            - -c
            - npx -y supergateway@4 --stdio 'npx -y [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: seo-tools-mcp-ywm
      namespace: mcp
    spec:
      selector:
        app: seo-tools-mcp-ywm
      ports:
      - port: 8000
        targetPort: http
        name: http
    
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T22:14:08+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:
      seo-tools-mcp-ywm:
        enabled: true
        replicas: 1
        port: 8000
        path: /mcp
        container:
          name: seo-tools-mcp-ywm
          image: node:22-alpine
          ports:
          - containerPort: 8000
            name: http
          env:
          - name: YANDEX_OAUTH_TOKEN
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: YANDEX_OAUTH_TOKEN
          - name: YWM_OAUTH_TOKEN
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: YWM_OAUTH_TOKEN
          - name: YANDEX_CLIENT_ID
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: YANDEX_CLIENT_ID
          - name: YANDEX_CLIENT_SECRET
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: YANDEX_CLIENT_SECRET
          - name: YWM_HOST_ID
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: YWM_HOST_ID
          - name: YWM_USER_ID
            valueFrom:
              secretKeyRef:
                name: mcp-credentials
                key: YWM_USER_ID
          args:
          - sh
          - -c
          - npx -y supergateway@4 --stdio 'npx -y [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

    The form opens with CHANGE_ME for each value you supply: YANDEX_OAUTH_TOKEN, YWM_OAUTH_TOKEN, YANDEX_CLIENT_ID, YANDEX_CLIENT_SECRET, YWM_HOST_ID, YWM_USER_ID. Fill them in before you deploy.

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

    azure

    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 [email protected]
    # env: YANDEX_OAUTH_TOKEN, YWM_OAUTH_TOKEN, YANDEX_CLIENT_ID, YANDEX_CLIENT_SECRET, YWM_HOST_ID, YWM_USER_ID
    {
      "mcpServers": {
        "seo-tools-mcp-ywm": {
          "command": "npx",
          "args": [
            "-y",
            "[email protected]"
          ],
          "env": {
            "YANDEX_OAUTH_TOKEN": "${YANDEX_OAUTH_TOKEN}",
            "YWM_OAUTH_TOKEN": "${YWM_OAUTH_TOKEN}",
            "YANDEX_CLIENT_ID": "${YANDEX_CLIENT_ID}",
            "YANDEX_CLIENT_SECRET": "${YANDEX_CLIENT_SECRET}",
            "YWM_HOST_ID": "${YWM_HOST_ID}",
            "YWM_USER_ID": "${YWM_USER_ID}"
          }
        }
      }
    }
    #!/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 seo-tools-mcp-ywm -e "YANDEX_OAUTH_TOKEN=${YANDEX_OAUTH_TOKEN}" -e "YWM_OAUTH_TOKEN=${YWM_OAUTH_TOKEN}" -e "YANDEX_CLIENT_ID=${YANDEX_CLIENT_ID}" -e "YANDEX_CLIENT_SECRET=${YANDEX_CLIENT_SECRET}" -e "YWM_HOST_ID=${YWM_HOST_ID}" -e "YWM_USER_ID=${YWM_USER_ID}" -- npx -y [email protected]
    
    {
      "mcpServers": {
        "seo-tools-mcp-ywm": {
          "command": "npx",
          "args": [
            "-y",
            "[email protected]"
          ],
          "env": {
            "YANDEX_OAUTH_TOKEN": "${YANDEX_OAUTH_TOKEN}",
            "YWM_OAUTH_TOKEN": "${YWM_OAUTH_TOKEN}",
            "YANDEX_CLIENT_ID": "${YANDEX_CLIENT_ID}",
            "YANDEX_CLIENT_SECRET": "${YANDEX_CLIENT_SECRET}",
            "YWM_HOST_ID": "${YWM_HOST_ID}",
            "YWM_USER_ID": "${YWM_USER_ID}"
          }
        }
      }
    }
    {
      "servers": {
        "seo-tools-mcp-ywm": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "[email protected]"
          ],
          "env": {
            "YANDEX_OAUTH_TOKEN": "${YANDEX_OAUTH_TOKEN}",
            "YWM_OAUTH_TOKEN": "${YWM_OAUTH_TOKEN}",
            "YANDEX_CLIENT_ID": "${YANDEX_CLIENT_ID}",
            "YANDEX_CLIENT_SECRET": "${YANDEX_CLIENT_SECRET}",
            "YWM_HOST_ID": "${YWM_HOST_ID}",
            "YWM_USER_ID": "${YWM_USER_ID}"
          }
        }
      }
    }
    name: my-agent
    target: local
    servers:
    - hub: io.github.antohins/seo-tools-mcp-ywm
    
    • 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.