LinkedIn MCP Server

A Python MCP server built for Docker and HTTP connections through a reverse proxy.

The entire implementation is written and maintained by coding agents under human direction. The project is distributed under the MIT License.

Development

Install Python 3.12 and uv, then run:

uv sync --locked
uv run mcp-linkedin

The server listens on 0.0.0.0:8000. MCP clients connect to http://localhost:8000/mcp. GET /health returns {"status":"ok"}. The MCP resource server://info provides the service name and version.

Related MCP server: mcp-gateway

MCP Test Lab

Two anonymous tools let you try the deployed server from ChatGPT:

The connection check defaults to Hello from ChatGPT; dice default to one six-sided die. See Try MCP Test Lab in ChatGPT for connection steps, example prompts, and the companion plugin skill.

uv run ruff check .
uv run ruff format --check .
uv run mypy
uv run pytest
uv build

The test suite enforces 100% line and branch coverage for the application. Strict type checks include tests and Python scripts. See quality checks for dependency audits, documentation checks, and the complete local workflow.

Docker

docker compose up --build -d
curl --fail http://localhost:8000/health
docker compose down

Compose publishes the service on 127.0.0.1:8000. An external reverse proxy can connect to that loopback port. A proxy container can connect to mcp-linkedin:8000 on a shared Docker network. The image runs as UID/GID 10001 and includes a health check. PORT sets the HTTP listening port; its default is 8000.

For published releases:

docker run --rm -p 127.0.0.1:8000:8000 ghcr.io/stmoelter/mcp-linkedin:0.1.0

Push a vMAJOR.MINOR.PATCH tag to trigger the release workflow. After verification, it publishes Linux AMD64/ARM64 images with version and sha-<commit> tags to GHCR. The workflow summary provides the image digest. See deployment for the proxy contract and release procedure.

Collaboration

Development follows Gitflow: main holds releases and development integrates features. Pull requests and successful CI checks govern updates to both branches. Read AGENTS.md for coding-agent instructions and architecture decisions for the project conventions.