linkedhelper-mcp
MCP Server that gives Claude read-only access to your LinkedHelper 2 local database — campaigns, leads, chat history and more.
Prerequisites
- LinkedHelper 2 installed and opened at least once
- Claude Desktop
Installation (Claude Desktop)
Open Claude Desktop → Settings → Developer → Edit Config and add:
{
"mcpServers": {
"linkedhelper": {
"command": "uvx",
"args": ["linkedhelper-mcp"],
"env": {
"LH_DEFAULT_ACCOUNT_EMAIL": "your-linkedin@email.com"
}
}
}
}
Save the file, then restart Claude Desktop. That's it — no Python install required.
LH_DEFAULT_ACCOUNT_EMAILis optional. If you only have one LinkedHelper account, you can omit theenvblock entirely.
Available Tools
| Tool | Description |
|---|---|
lh_get_accounts |
List all LinkedHelper accounts on this machine |
lh_get_campaigns |
List campaigns (active or including archived) |
lh_get_campaign_detail |
Campaign details: actions, total leads |
lh_get_campaign_leads |
Leads in a campaign, with reply filter |
lh_get_chat_history |
Chat threads with outbound/inbound direction |
lh_get_person_detail |
Full profile: email, location, company, tags, notes |
lh_search_people |
Search leads by name or headline |
lh_get_action_results |
Action execution results per campaign |
Example prompts for Claude
- "Show me all active campaigns"
- "Who replied to the Outreach campaign?"
- "Give me full details for person ID 42"
- "Search for people with CTO in their headline"
- "Show my chat history with Nguyen Huan"
Configuration
Environment variables (all optional):
| Variable | Description |
|---|---|
LH_DEFAULT_ACCOUNT_EMAIL |
Email of the LinkedIn account to use by default |
LH_BASE_DIR |
Override LinkedHelper data directory (if installed in a custom path) |
LinkedHelper data is stored at:
- Linux/macOS:
~/.config/linked-helper//~/Library/Application Support/linked-helper/ - Windows:
%APPDATA%\linked-helper\
License
MIT
Metadata
Release files for linkedhelper-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| linkedhelper_mcp-0.1.0.tar.gz | 13.8 kB | Without provenance | Details for linkedhelper_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| linkedhelper_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for linkedhelper_mcp-0.1.0-py3-none-any.whl |
Total release size: 27.9 kB
Release files / linkedhelper_mcp-0.1.0.tar.gz
| Download URL | linkedhelper_mcp-0.1.0.tar.gz |
|---|---|
| Size | 13.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d8b4b5e74757f85ae96b9a296d2244a6af580d99f3fcc77b2298333ea114907
|
|
BLAKE2b-256 checksum How to use checksums |
b154a0a24a8226b2ba18b09c0228f2aed2369813ce03ff5afcd7f21344e335e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / linkedhelper_mcp-0.1.0-py3-none-any.whl
| Download URL | linkedhelper_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26113ad6898f627d286aea4985d32758478abca48aad0e4c2cf2eafb236714fe
|
|
BLAKE2b-256 checksum How to use checksums |
9690128b17f28b7c416f15b1b38d6dc652431dbb89f5f06e46fda10a2feba7f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for linkedhelper-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.