HDW MCP Server

by MCP-Mirror

303 downloads Not rated yet Activity

GitHub Website

Other

About

A Model Context Protocol server that provides comprehensive access to LinkedIn data and account management through the HorizonDataWave API. It enables user and company searches, profile lookups, email resolution, post/reaction retrieval, and direct actions such as sending chat…

Details

License: Activity

Explore

- LinkedIn Users Search: Filter and search for LinkedIn users by keywords, name, title, company, location, industry, and education.
- Profile Lookup: Retrieve detailed profile information for a LinkedIn user.
- Email Lookup: Find LinkedIn user details by email address.
- Posts & Reactions: Retrieve a user's posts and associated reactions.
- Post Reposts & Comments: Retrieve reposts and comments for a specific LinkedIn post.
- Account Management:
- Chat Functionality: Retrieve and send chat messages via the LinkedIn management API.
- Connection Management: Send connection invitations to LinkedIn users.
- Post Commenting: Create comments on LinkedIn posts or replies.
- User Connections: Retrieve a list of a user's LinkedIn connections.
- Company Search & Details:
- Google Company Search: Find LinkedIn companies using Google search – the first result is typically the best match.
- Company Lookup: Retrieve detailed information about a LinkedIn company.
- Company Employees: Retrieve employees for a given LinkedIn company.

- Google Search

---

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name HDW MCP Server

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

From the repository

npm install

Create a .env file in the root of your project with the following content:

env
HDW_ACCESS_TOKEN=YOUR_HD_W_ACCESS_TOKEN
HDW_ACCOUNT_ID=YOUR_HD_W_ACCOUNT_ID

Below is an example configuration for an MCP client (e.g., a custom integration):

json
{
"mcpServers": {
"hdw": {
"command": "npx",
"args": ["@horizondatawave/mcp"],
"env": {
"HDW_ACCESS_TOKEN": "YOUR_HD_W_ACCESS_TOKEN",
"HDW_ACCOUNT_ID": "YOUR_HD_W_ACCOUNT_ID"
}
}
}
}
```
Replace the paths and credentials with your own values.

`keywords`

(optional): Any keyword for search.

`first_name`

, `last_name`, `title`, `company_keywords`, `school_keywords` (optional).

`current_company`

, `past_company`, `location`, `industry`, `education` (optional).

`count`

(optional, default: 10): Maximum number of results (max 1000).

`timeout`

(optional, default: 300): Timeout in seconds (20–1500).

`user`

(required): User alias, URL, or URN.

`with_experience`

, `with_education`, `with_skills` (optional, default: true).

`email`

(required): Email address.

`urn`

(required): User URN (must include prefix, e.g. `fsd_profile:...`).

`text`

(required): Message text.

`connected_after`

(optional): Timestamp filter.

`sort`

(optional, default: `"relevance"`; allowed values: `"relevance"`, `"recent"`).

`with_urn`

(optional, default: false).

`count_per_keyword`

(optional, default: 1; range 1–10).

`company`

(required): Company alias, URL, or URN.

`companies`

(required): Array of company URNs.

HDW MCP Server exposes several tools through the MCP protocol. Each tool is defined with its name, description, and input parameters:

1. Search LinkedIn Users
Name: search_linkedin_users
Description: Search for LinkedIn users with various filters.
Parameters:
- keywords (optional): Any keyword for search.
- first_name, last_name, title, company_keywords, school_keywords (optional).
- current_company, past_company, location, industry, education (optional).
- count (optional, default: 10): Maximum number of results (max 1000).
- timeout (optional, default: 300): Timeout in seconds (20–1500).

2. Get LinkedIn Profile
Name: get_linkedin_profile
Description: Retrieve detailed profile information about a LinkedIn user.
Parameters:
- user (required): User alias, URL, or URN.
- with_experience, with_education, with_skills (optional, default: true).

3. Get LinkedIn Email User
Name: get_linkedin_email_user
Description: Look up LinkedIn user details by email.
Parameters:
- email (required): Email address.
- count (optional, default: 5).
- timeout (optional, default: 300).

4. Get LinkedIn User Posts
Name: get_linkedin_user_posts
Description: Retrieve posts for a LinkedIn user by URN.
Parameters:
- urn (required): User URN (must include prefix, e.g. fsd_profile:...).
- count (optional, default: 10).
- timeout (optional, default: 300).

5. Get LinkedIn User Reactions
Name: get_linkedin_user_reactions
Description: Retrieve reactions for a LinkedIn user by URN.
Parameters:
- urn (required).
- count (optional, default: 10).
- timeout (optional, default: 300).

6. Get LinkedIn Chat Messages
Name: get_linkedin_chat_messages
Description: Retrieve top chat messages from the LinkedIn management API.
Parameters:
- user (required): User URN (with prefix).
- count (optional, default: 20).
- timeout (optional, default: 300).

7. Send LinkedIn Chat Message
Name: send_linkedin_chat_message
Description: Send a chat message using the LinkedIn management API.
Parameters:
- user (required): Recipient user URN (with prefix).
- text (required): Message text.
- timeout (optional, default: 300).

8. Send LinkedIn Connection Request
Name: send_linkedin_connection
Description: Send a connection invitation to a LinkedIn user.
Parameters:
- user (required).
- timeout (optional, default: 300).

9. Send LinkedIn Post Comment
Name: send_linkedin_post_comment
Description: Create a comment on a LinkedIn post or reply.
Parameters:
- text (required): Comment text.
- urn (required): Activity or comment URN.
- timeout (optional, default: 300).

10. Get LinkedIn User Connections
Name: get_linkedin_user_connections
Description: Retrieve a list of LinkedIn user connections.
Parameters:
- connected_after (optional): Timestamp filter.
- count (optional, default: 20).
- timeout (optional, default: 300).

11. Get LinkedIn Post Reposts
Name: get_linkedin_post_reposts
Description: Retrieve reposts for a LinkedIn post.
Parameters:
- urn (required): Post URN (must start with activity:).
- count (optional, default: 10).
- timeout (optional, default: 300).

12. Get LinkedIn Post Comments
Name: get_linkedin_post_comments
Description: Retrieve comments for a LinkedIn post.
Parameters:
- urn (required).
- sort (optional, default: "relevance"; allowed values: "relevance", "recent").
- count (optional, default: 10).
- timeout (optional, default: 300).

13. Get LinkedIn Google Company
Name: get_linkedin_google_company
Description: Search for LinkedIn companies via Google – the first result is typically the best match.
Parameters:
- keywords (required): Array of company keywords.
- with_urn (optional, default: false).
- count_per_keyword (optional, default: 1; range 1–10).
- timeout (optional, default: 300).

14. Get LinkedIn Company
Name: get_linkedin_company
Description: Retrieve detailed information about a LinkedIn company.
Parameters:
- company (required): Company alias, URL, or URN.
- timeout (optional, default: 300).

15. Get LinkedIn Company Employees
Name: get_linkedin_company_employees
Description: Retrieve employees of a LinkedIn company.
Parameters:
- companies (required): Array of company URNs.
- keywords, first_name, last_name (optional).
- count (optional, default: 10).
- timeout (optional, default: 300).

---

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "hdw mcp server": {
            "hdw": {
                "command": "npx",
                "args": [
                    "@horizondatawave/mcp"
                ],
                "env": {
                    "HDW_ACCESS_TOKEN": "",
                    "HDW_ACCOUNT_ID": ""
                }
            }
        }
    }
}

McpServers

{
    "hdw": {
        "command": "npx",
        "args": [
            "@horizondatawave/mcp"
        ],
        "env": {
            "HDW_ACCESS_TOKEN": "",
            "HDW_ACCOUNT_ID": ""
        }
    }
}

A Model Context Protocol (MCP) server that provides comprehensive access to LinkedIn data and functionalities using the HorizonDataWave API, enabling not only data retrieval but also robust management of user accounts.
---

Features

---

Tools

HDW MCP Server exposes several tools through the MCP protocol. Each tool is defined with its name, description, and input parameters:

---

Setup Guide

1. Clone the Repository (macOS)

Open your terminal and run the following commands:

```bash

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Explore

Setting up with Highlight

From the repository

keywords

first_name

current_company

count

timeout

user

with_experience

email

urn

text

connected_after

sort

with_urn

count_per_keyword

company

companies

Claude Desktop / Cursor

McpServers

Features

Tools

Setup Guide

1. Clone the Repository (macOS)

More like this

Sequential Thinking

Filesystem

EverArt

Google Drive

`keywords`

`first_name`

`current_company`

`count`

`timeout`

`user`

`with_experience`

`email`

`urn`

`text`

`connected_after`

`sort`

`with_urn`

`count_per_keyword`

`company`

`companies`