LinkedIn Intelligence & Research MCP Server
# LinkedIn Intelligence & Research MCP Server
> A production-ready Model Context Protocol (MCP) server for LinkedIn Profile & Activity Intelligence, Deep 15-Dimension Post Analysis, Business Signal Detection (GA4, GTM, Meta CAPI), Prospect ICP Matching, and Sales Opportunity Discovery.





---
## 📌 Features
- 🕵️ **`linkedin_research_profile` Orchestrator**: High-level command that runs end-to-end profile research, normalizes activity, extracts topics, detects signals, evaluates ICP match, and returns actionable outreach angles.
- 👤 **Static Profile Intelligence (`linkedin_analyze_profile`)**: Analyzes headline, about section, role, company size, and positioning.
- 📝 **Deep Post Analyzer (`linkedin_analyze_post`)**: 15-dimension post matrix (Topic, Post Type, Hook, Audience, Intent, Tone, CTA, Pain Points, Tools, Sentiment, Commercial Intent).
- 📡 **Business Signal Detector (`linkedin_detect_business_signals`)**: Identifies Growth (hiring, expansion), Marketing (funnels, CRM), and Technical Tracking signals (GA4, GTM, Meta CAPI, Attribution).
- 🎯 **ICP Prospect Matcher (`linkedin_analyze_prospect`)**: Evaluates profile fit against custom Ideal Customer Profile rules with confidence scoring.
- 💡 **Opportunity Finder (`linkedin_find_opportunities`)**: Maps user discussions into technical tracking service opportunities (e.g. GA4 offline conversion tracking).
- 📅 **Activity Timeline (`linkedin_build_activity_timeline`)**: Constructs a chronological summary of professional activity over custom date ranges.
- 📑 **MCP Resources (`linkedin://`)**: Exposes static/dynamic URIs (`linkedin://profiles/{id}`, `linkedin://profiles/{id}/analysis`, `linkedin://profiles/{id}/signals`).
- 💬 **MCP Prompts**: Includes reusable prompt workflows (`/profile-analysis`, `/prospect-analysis`, `/find-tracking-opportunities`).
---
## 🛠️ Installation & Build
```bash
# Install dependencies
npm install
# Run Vitest unit test suite
npm test
# Compile TypeScript to dist/
npm run build
# Start MCP server on stdio transport
npm start
```
---
## ⚙️ MCP Client Configuration
### Cursor IDE Configuration
Add to `.cursor/mcp.json` or Cursor MCP Settings:
```json
{
"mcpServers": {
"linkedin-intelligence-mcp": {
"command": "node",
"args": ["C:/Users/FLS/.gemini/antigravity/scratch/linkedin-mcp-server/dist/index.js"]
}
}
}
```
### Antigravity Configuration
Add to `.gemini/antigravity/mcp_config.json`:
```json
{
"mcpServers": {
"linkedin-intelligence-mcp": {
"command": "node",
"args": ["C:/Users/FLS/.gemini/antigravity/scratch/linkedin-mcp-server/dist/index.js"]
}
}
}
```
---
## 📄 License
Licensed under the [MIT License](LICENSE).
TDQS
Scored across 20 tools
At least two pairs (research_profile vs analyze_prospect, build_lead_search vs generate_boolean_search) have heavily overlapping scopes, and extract_topics overlaps with analyze_recent_activity. Most other tools are clearly separated by noun and verb, so descriptions resolve most ambiguity, but the overlap is notable.
All 20 tools follow the linkedin_ prefix plus verb_noun snake_case pattern. Verbs are consistent lowercase and the noun indicates the target resource, making tool names highly predictable.
20 tools is on the upper end of typical server size, bordering on heavy. However, the tools form a coherent pipeline spanning activity retrieval, profile/post analysis, signal detection, lead search, scoring, and prospect orchestration, so the count is reasonably justified.
The server covers the full lead-research workflow: getting and analyzing activity, researching profiles, detecting signals, finding opportunities, building searches, importing/analyzing results, filtering/ranking, and scoring. Minor gaps include standalone company analysis or direct LinkedIn profile lookup, but these are workaroundable.