x=hub

your toolset

    build deployment
    sign in

    mcp-jira-scoped

    mcpkey · package
    io.github.deepwired/mcp-jira-scoped · v1.0.0
    deploy just this

    Jira MCP server with scoped API tokens via api.atlassian.com gateway

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

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

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    docker run --rm -p 127.0.0.1:8101:8000 -e JIRA_INSTANCE -e JIRA_USER_EMAIL -e JIRA_API_TOKEN -e JIRA_SCOPES -e JIRA_CLOUD_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-18T23:56:25+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:
  jira-scoped:
    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:
      JIRA_INSTANCE: ${JIRA_INSTANCE}
      JIRA_USER_EMAIL: ${JIRA_USER_EMAIL}
      JIRA_API_TOKEN: ${JIRA_API_TOKEN}
      JIRA_SCOPES: ${JIRA_SCOPES}
      JIRA_CLOUD_ID: ${JIRA_CLOUD_ID}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T23:56:25+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: jira-scoped
  namespace: mcp
  labels: &id001
    app: jira-scoped
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: jira-scoped
        image: node:22-alpine
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: JIRA_INSTANCE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: JIRA_INSTANCE
        - name: JIRA_USER_EMAIL
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: JIRA_USER_EMAIL
        - name: JIRA_API_TOKEN
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: JIRA_API_TOKEN
        - name: JIRA_SCOPES
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: JIRA_SCOPES
        - name: JIRA_CLOUD_ID
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: JIRA_CLOUD_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: jira-scoped
  namespace: mcp
spec:
  selector:
    app: jira-scoped
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    # Generated by Hub for toolset "my-agent" (2026-10-18T23:56:25+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:
  jira-scoped:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: jira-scoped
      image: node:22-alpine
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: JIRA_INSTANCE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: JIRA_INSTANCE
      - name: JIRA_USER_EMAIL
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: JIRA_USER_EMAIL
      - name: JIRA_API_TOKEN
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: JIRA_API_TOKEN
      - name: JIRA_SCOPES
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: JIRA_SCOPES
      - name: JIRA_CLOUD_ID
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: JIRA_CLOUD_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
    deploy to koyeb

    The form opens with CHANGE_ME for each value you supply: JIRA_INSTANCE, JIRA_USER_EMAIL, JIRA_API_TOKEN, JIRA_SCOPES, JIRA_CLOUD_ID. 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: JIRA_INSTANCE, JIRA_USER_EMAIL, JIRA_API_TOKEN, JIRA_SCOPES, JIRA_CLOUD_ID
    {
  "mcpServers": {
    "jira-scoped": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "JIRA_INSTANCE": "${JIRA_INSTANCE}",
        "JIRA_USER_EMAIL": "${JIRA_USER_EMAIL}",
        "JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
        "JIRA_SCOPES": "${JIRA_SCOPES}",
        "JIRA_CLOUD_ID": "${JIRA_CLOUD_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 jira-scoped -e "JIRA_INSTANCE=${JIRA_INSTANCE}" -e "JIRA_USER_EMAIL=${JIRA_USER_EMAIL}" -e "JIRA_API_TOKEN=${JIRA_API_TOKEN}" -e "JIRA_SCOPES=${JIRA_SCOPES}" -e "JIRA_CLOUD_ID=${JIRA_CLOUD_ID}" -- npx -y [email protected]

    {
  "mcpServers": {
    "jira-scoped": {
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "JIRA_INSTANCE": "${JIRA_INSTANCE}",
        "JIRA_USER_EMAIL": "${JIRA_USER_EMAIL}",
        "JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
        "JIRA_SCOPES": "${JIRA_SCOPES}",
        "JIRA_CLOUD_ID": "${JIRA_CLOUD_ID}"
      }
    }
  }
}
    {
  "servers": {
    "jira-scoped": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "[email protected]"
      ],
      "env": {
        "JIRA_INSTANCE": "${JIRA_INSTANCE}",
        "JIRA_USER_EMAIL": "${JIRA_USER_EMAIL}",
        "JIRA_API_TOKEN": "${JIRA_API_TOKEN}",
        "JIRA_SCOPES": "${JIRA_SCOPES}",
        "JIRA_CLOUD_ID": "${JIRA_CLOUD_ID}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.github.deepwired/mcp-jira-scoped
    • 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.