LinkedIn MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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-linkedinThe 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:
Tool | Inputs | Result |
| Optional | Echoed message, server name, installed version |
|
| Individual rolls and their sum |
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 buildThe 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 downCompose 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.0Push 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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Host any HTTP API as a standard MCP server; auto-distribute to 12+ mainstream agent platforms.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
MCP gateway and cloud hosting for MCP servers, agents and apps like RAG, managed from your agent.
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA minimal, containerized MCP server that exposes a Streamable HTTP transport with API key authentication, allowing secure access to MCP endpoints.-
- AlicenseNot gradedqualityBmaintenanceEnables multiple MCP clients to securely access various third-party MCP backends through a single HTTP gateway, with modern MCP handshake compatibility and session lifecycle management.53 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect, list tools, and invoke the echo tool over HTTP.MIT
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to connect to a streamable HTTP server with multiple tools, secured by API key authentication, rate limiting, and health checks via an nginx gateway for Docker-based deployment.-