x=hub

your toolset

    build deployment
    sign in

    EWS Meeting MCP

    mcpkey · package
    io.github.ap311036/ews-meeting-mcp · v0.1.17
    deploy just this

    Safely schedule Outlook meetings on on-prem Exchange EWS with preview-confirmed writes.

    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/ews-meeting
# ews-meeting: 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-ews-meeting.service 2>/dev/null || true
as_mcp /var/lib/mcp/ews-meeting rm -rf /var/lib/mcp/ews-meeting/.npm/_npx
as_mcp /var/lib/mcp/ews-meeting npx --yes [email protected] -- true
as_mcp /var/lib/mcp/ews-meeting npx --yes --package=supergateway@4 -- true

#!/usr/bin/env bash
# ews-meeting (io.github.ap311036/ews-meeting-mcp), recipe baremetal (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-ews-meeting.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 ews-meeting (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/ews-meeting
WorkingDirectory=/var/lib/mcp/ews-meeting
ExecStart=/opt/mcp/my-agent/bin/ews-meeting.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/ews-meeting

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e EWS_ENDPOINT -e EWS_EMAIL -e EWS_USERNAME -e EWS_PASSWORD -e EWS_PASSWORD_KEYCHAIN_SERVICE -e EWS_PASSWORD_KEYCHAIN_ACCOUNT -e EWS_AUTH_TYPE -e EWS_TIMEZONE 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-19T01:47:32+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:
  ews-meeting:
    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:
      EWS_ENDPOINT: ${EWS_ENDPOINT}
      EWS_EMAIL: ${EWS_EMAIL}
      EWS_USERNAME: ${EWS_USERNAME}
      EWS_PASSWORD: ${EWS_PASSWORD}
      EWS_PASSWORD_KEYCHAIN_SERVICE: ${EWS_PASSWORD_KEYCHAIN_SERVICE}
      EWS_PASSWORD_KEYCHAIN_ACCOUNT: ${EWS_PASSWORD_KEYCHAIN_ACCOUNT}
      EWS_AUTH_TYPE: ${EWS_AUTH_TYPE}
      EWS_TIMEZONE: ${EWS_TIMEZONE}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-19T01:47:32+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: ews-meeting
  namespace: mcp
  labels: &id001
    app: ews-meeting
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: ews-meeting
        image: node:22-alpine
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: EWS_ENDPOINT
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_ENDPOINT
        - name: EWS_EMAIL
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_EMAIL
        - name: EWS_USERNAME
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_USERNAME
        - name: EWS_PASSWORD
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_PASSWORD
        - name: EWS_PASSWORD_KEYCHAIN_SERVICE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_PASSWORD_KEYCHAIN_SERVICE
        - name: EWS_PASSWORD_KEYCHAIN_ACCOUNT
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_PASSWORD_KEYCHAIN_ACCOUNT
        - name: EWS_AUTH_TYPE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_AUTH_TYPE
        - name: EWS_TIMEZONE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: EWS_TIMEZONE
        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: ews-meeting
  namespace: mcp
spec:
  selector:
    app: ews-meeting
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-19T01:47:32+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:
  ews-meeting:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: ews-meeting
      image: node:22-alpine
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: EWS_ENDPOINT
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_ENDPOINT
      - name: EWS_EMAIL
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_EMAIL
      - name: EWS_USERNAME
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_USERNAME
      - name: EWS_PASSWORD
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_PASSWORD
      - name: EWS_PASSWORD_KEYCHAIN_SERVICE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_PASSWORD_KEYCHAIN_SERVICE
      - name: EWS_PASSWORD_KEYCHAIN_ACCOUNT
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_PASSWORD_KEYCHAIN_ACCOUNT
      - name: EWS_AUTH_TYPE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_AUTH_TYPE
      - name: EWS_TIMEZONE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: EWS_TIMEZONE
      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
    deploy to koyeb

    The form opens with CHANGE_ME for each value you supply: EWS_ENDPOINT, EWS_EMAIL, EWS_USERNAME, EWS_PASSWORD, EWS_PASSWORD_KEYCHAIN_SERVICE, EWS_PASSWORD_KEYCHAIN_ACCOUNT, EWS_AUTH_TYPE, EWS_TIMEZONE. 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 [email protected]
# env: EWS_ENDPOINT, EWS_EMAIL, EWS_USERNAME, EWS_PASSWORD, EWS_PASSWORD_KEYCHAIN_SERVICE, EWS_PASSWORD_KEYCHAIN_ACCOUNT, EWS_AUTH_TYPE, EWS_TIMEZONE
    {
  "mcpServers": {
    "ews-meeting": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "EWS_ENDPOINT": "${EWS_ENDPOINT}",
        "EWS_EMAIL": "${EWS_EMAIL}",
        "EWS_USERNAME": "${EWS_USERNAME}",
        "EWS_PASSWORD": "${EWS_PASSWORD}",
        "EWS_PASSWORD_KEYCHAIN_SERVICE": "${EWS_PASSWORD_KEYCHAIN_SERVICE}",
        "EWS_PASSWORD_KEYCHAIN_ACCOUNT": "${EWS_PASSWORD_KEYCHAIN_ACCOUNT}",
        "EWS_AUTH_TYPE": "${EWS_AUTH_TYPE}",
        "EWS_TIMEZONE": "${EWS_TIMEZONE}"
      }
    }
  }
}
    #!/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 ews-meeting -e "EWS_ENDPOINT=${EWS_ENDPOINT}" -e "EWS_EMAIL=${EWS_EMAIL}" -e "EWS_USERNAME=${EWS_USERNAME}" -e "EWS_PASSWORD=${EWS_PASSWORD}" -e "EWS_PASSWORD_KEYCHAIN_SERVICE=${EWS_PASSWORD_KEYCHAIN_SERVICE}" -e "EWS_PASSWORD_KEYCHAIN_ACCOUNT=${EWS_PASSWORD_KEYCHAIN_ACCOUNT}" -e "EWS_AUTH_TYPE=${EWS_AUTH_TYPE}" -e "EWS_TIMEZONE=${EWS_TIMEZONE}" -- npx -y [email protected]

    {
  "mcpServers": {
    "ews-meeting": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "EWS_ENDPOINT": "${EWS_ENDPOINT}",
        "EWS_EMAIL": "${EWS_EMAIL}",
        "EWS_USERNAME": "${EWS_USERNAME}",
        "EWS_PASSWORD": "${EWS_PASSWORD}",
        "EWS_PASSWORD_KEYCHAIN_SERVICE": "${EWS_PASSWORD_KEYCHAIN_SERVICE}",
        "EWS_PASSWORD_KEYCHAIN_ACCOUNT": "${EWS_PASSWORD_KEYCHAIN_ACCOUNT}",
        "EWS_AUTH_TYPE": "${EWS_AUTH_TYPE}",
        "EWS_TIMEZONE": "${EWS_TIMEZONE}"
      }
    }
  }
}
    {
  "servers": {
    "ews-meeting": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "EWS_ENDPOINT": "${EWS_ENDPOINT}",
        "EWS_EMAIL": "${EWS_EMAIL}",
        "EWS_USERNAME": "${EWS_USERNAME}",
        "EWS_PASSWORD": "${EWS_PASSWORD}",
        "EWS_PASSWORD_KEYCHAIN_SERVICE": "${EWS_PASSWORD_KEYCHAIN_SERVICE}",
        "EWS_PASSWORD_KEYCHAIN_ACCOUNT": "${EWS_PASSWORD_KEYCHAIN_ACCOUNT}",
        "EWS_AUTH_TYPE": "${EWS_AUTH_TYPE}",
        "EWS_TIMEZONE": "${EWS_TIMEZONE}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.ap311036/ews-meeting-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.