x=hub

your toolset

    build deployment
    sign in

    LinkedIn

    mcpother
    io.docker.mcp/linkedin-mcp-server · vc54e3fa518d2
    deploy just this

    This MCP server allows Claude and other AI assistants to access your LinkedIn. Scrape LinkedIn profiles and companies, get your recommended jobs, and perform job searches. Set your li_at LinkedIn cookie to use this server.

    run it

    on your own machines, one way per deploy method
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    #!/usr/bin/env bash
# linkedin (io.docker.mcp/linkedin-mcp-server), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-linkedin.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-linkedin -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env stickerdaniel/linkedin-mcp-server:1.4.0

[Unit]
Description=MCP server linkedin (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target

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

[Install]
WantedBy=multi-user.target
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    docker run --rm -p 127.0.0.1:8101:8000 -e LINKEDIN_COOKIE stickerdaniel/linkedin-mcp-server:1.4.0
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T08:58:22+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:
  linkedin:
    image: stickerdaniel/linkedin-mcp-server:1.4.0
    ports:
    - 127.0.0.1:8101:8000
    restart: unless-stopped
    x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
      HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
      instead.'
    environment:
      LINKEDIN_COOKIE: ${LINKEDIN_COOKIE}
volumes:
  npm-cache: {}
  uv-cache: {}
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T08:58:22+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: linkedin
  namespace: mcp
  labels: &id001
    app: linkedin
spec:
  replicas: 1
  selector:
    matchLabels: *id001
  template:
    metadata:
      labels: *id001
    spec:
      containers:
      - name: linkedin
        image: stickerdaniel/linkedin-mcp-server:1.4.0
        ports:
        - containerPort: 8000
          name: http
        env:
        - name: LINKEDIN_COOKIE
          valueFrom:
            secretKeyRef:
              name: mcp-credentials
              key: LINKEDIN_COOKIE
---
apiVersion: v1
kind: Service
metadata:
  name: linkedin
  namespace: mcp
spec:
  selector:
    app: linkedin
  ports:
  - port: 8000
    targetPort: http
    name: http
    generated from the record, not tested yet
    CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
    # Generated by Hub for toolset "my-agent" (2026-10-18T08:58:22+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:
  linkedin:
    enabled: true
    replicas: 1
    port: 8000
    path: /mcp
    container:
      name: linkedin
      image: stickerdaniel/linkedin-mcp-server:1.4.0
      ports:
      - containerPort: 8000
        name: http
      env:
      - name: LINKEDIN_COOKIE
        valueFrom:
          secretKeyRef:
            name: mcp-credentials
            key: LINKEDIN_COOKIE

# 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: LINKEDIN_COOKIE. 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
    docker run -i --rm -e LINKEDIN_COOKIE stickerdaniel/linkedin-mcp-server:1.4.0
    {
  "mcpServers": {
    "linkedin": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "LINKEDIN_COOKIE",
        "stickerdaniel/linkedin-mcp-server:1.4.0"
      ],
      "env": {
        "LINKEDIN_COOKIE": "${LINKEDIN_COOKIE}"
      }
    }
  }
}
    #!/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 linkedin -e "LINKEDIN_COOKIE=${LINKEDIN_COOKIE}" -- docker run -i --rm -e LINKEDIN_COOKIE stickerdaniel/linkedin-mcp-server:1.4.0

    {
  "mcpServers": {
    "linkedin": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "LINKEDIN_COOKIE",
        "stickerdaniel/linkedin-mcp-server:1.4.0"
      ],
      "env": {
        "LINKEDIN_COOKIE": "${LINKEDIN_COOKIE}"
      }
    }
  }
}
    {
  "servers": {
    "linkedin": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "LINKEDIN_COOKIE",
        "stickerdaniel/linkedin-mcp-server:1.4.0"
      ],
      "env": {
        "LINKEDIN_COOKIE": "${LINKEDIN_COOKIE}"
      }
    }
  }
}
    name: my-agent
target: local
servers:
- hub: io.docker.mcp/linkedin-mcp-server
    • 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.