Pipeline MCP Server

MCP (Model Context Protocol) server for Pipeline - AI-powered LinkedIn outreach automation.

Control your LinkedIn campaigns, manage prospects, track buying signals, monitor workflow performance, and view conversations directly from Claude, ChatGPT, Cursor, or any MCP-compatible AI assistant.

Features

• 40 Tools across 7 categories
• Campaign Management - Create, start, pause, resume, clone campaigns
• Prospect Management - Add, remove, filter prospects by ICP score
• Analytics - Campaign metrics, reply rates, ICP distribution, top performers
• LinkedIn Accounts - Monitor daily usage, check InMail balance
• Workflow Monitoring - Track execution progress, pending and failed actions
• Conversations - View replies, search conversations, get message threads
• Signal Tracking - Monitor buying signals, create trackers, act on signals

Quick Start

Installation

npm install -g pipeline-mcp

Or use with npx:

npx pipeline-mcp --api-key YOUR_API_KEY

Claude Code Configuration

Add to your Claude Code settings (~/.claude/settings.json):

{
  "mcpServers": {
    "pipeline": {
      "command": "npx",
      "args": ["-y", "pipeline-mcp", "--api-key", "YOUR_API_KEY"]
    }
  }
}

Claude Desktop Configuration

Add to your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "pipeline": {
      "command": "npx",
      "args": ["-y", "pipeline-mcp", "--api-key", "YOUR_API_KEY"]
    }
  }
}

Cursor IDE Configuration

Add to your Cursor settings:

{
  "mcp": {
    "servers": {
      "pipeline": {
        "command": "npx",
        "args": ["-y", "pipeline-mcp", "--api-key", "YOUR_API_KEY"]
      }
    }
  }
}

Usage Examples

Once connected, you can ask your AI assistant:

• "How are my campaigns doing?"
• "Show me prospects with ICP score above 80"
• "Who replied to my campaigns this week?"
• "Add linkedin.com/in/johndoe to my VP Sales campaign"
• "Which campaign has the best reply rate?"
• "How many InMails do I have left?"
• "Show me failed actions in my campaign"
• "What buying signals have been detected?"
• "Compare my active campaigns side by side"
• "Clone my best campaign and rename it"

Available Tools

Campaign Management (7 tools)

| Tool | Description | |------|-------------| | list-campaigns | List all campaigns with optional status filter | | get-campaign | Get detailed campaign information | | create-campaign | Create a new campaign | | start-campaign | Start campaign execution | | pause-campaign | Pause a running campaign | | resume-campaign | Resume a paused campaign | | clone-campaign | Clone an existing campaign |

Prospect Management (7 tools)

| Tool | Description | |------|-------------| | list-prospects | List prospects with ICP score filtering | | get-prospect | Get prospect details | | add-prospect | Add a single prospect | | add-prospects-bulk | Add up to 1000 prospects at once | | remove-prospect | Remove a prospect | | get-prospect-stats | Get pipeline breakdown by status | | list-prospect-lists | List all prospect lists |

Analytics (6 tools)

| Tool | Description | |------|-------------| | get-campaign-analytics | Get campaign performance metrics | | get-account-analytics | Get account-wide analytics | | get-reply-analytics | Get reply rates and sentiment breakdown | | get-icp-distribution | Get ICP score distribution across prospects | | compare-campaigns | Compare multiple campaigns side by side | | get-top-performers | Get best performing campaigns by metric |

LinkedIn Accounts (4 tools)

| Tool | Description | |------|-------------| | list-linkedin-accounts | List connected LinkedIn accounts | | get-linkedin-account | Get account details and limits | | get-daily-usage | Get today's usage vs daily limits | | get-inmail-balance | Check InMail credits remaining |

Workflow Monitoring (4 tools)

| Tool | Description | |------|-------------| | get-workflow-status | Get execution status and progress for a campaign | | get-pending-actions | List pending workflow actions | | get-failed-actions | List failed actions with error details | | get-execution-progress | Get progress percentage and ETA |

Conversations (4 tools)

| Tool | Description | |------|-------------| | list-conversations | List conversations, filter by campaign or reply status | | get-conversation | Get full message thread for a conversation | | get-recent-replies | Get most recent replies across all campaigns | | search-conversations | Search conversations by keyword |

Signal Tracking (8 tools)

| Tool | Description | |------|-------------| | list-signals | List detected buying signals | | list-signal-trackers | List configured signal trackers | | create-signal-tracker | Create a new keyword tracker | | pause-signal-tracker | Pause a tracker | | resume-signal-tracker | Resume a tracker | | add-signal-to-campaign | Add signal prospect to a campaign | | create-prospect-from-signal | Create a prospect from a detected signal | | trigger-signal-poll | Manually trigger signal polling |

HTTP Server Mode

For integrations with n8n, Clay, or custom applications:

pipeline-mcp --http --port 3000

Authentication via headers:

• X-API-KEY: your_api_key
• Authorization: Bearer your_api_key

JSON-RPC Examples

# List available tools
curl -X POST http://localhost:3000 \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: your_api_key" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

# Call a tool
curl -X POST http://localhost:3000 \
  -H "Content-Type: application/json" \
  -H "X-API-KEY: your_api_key" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "list-campaigns",
      "arguments": { "status": "active" }
    }
  }'

Environment Variables

| Variable | Description | |----------|-------------| | PIPELINE_API_KEY | Your Pipeline API key | | PIPELINE_BASE_URL | Custom API URL (default: https://pipeline.help/api) |

CLI Options

Options:
  --api-key <key>     Your Pipeline API key
  --base-url <url>    Custom API base URL
  --port <number>     Port for HTTP server (default: 3000)
  --http              Run in HTTP server mode
  --stdio             Run in stdio mode (default)
  --version, -v       Show version
  --help, -h          Show help

Development

# Clone the repository
git clone https://github.com/mattvinall/pipeline-mcp.git
cd pipeline-mcp

# Install dependencies
npm install

# Build
npm run build

# Run tests
npm test

# Run in development (watch mode)
npm run dev

Docker

FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm install
COPY . .
RUN npm run build
EXPOSE 3000
CMD ["node", "dist/index.js", "--http"]

docker build -t pipeline-mcp .
docker run -p 3000:3000 -e PIPELINE_API_KEY=your_key pipeline-mcp

Getting Your API Key

1. Log in to Pipeline
2. Go to Settings > API Keys
3. Create a new API key
4. Copy the key and use it with this MCP server

Support

• GitHub Issues

License

MIT