Forge MCP Server

A remote MCP server that connects AI assistants to the full Salesforge product suite: Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge.

Built on the Model Context Protocol, works with Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible client.

Supported Products

Salesforge (71 tools) - Workspaces, contacts, sequences and subsequences, mailboxes, LinkedIn accounts, sender profiles, tags, enrollment preflight and confirmation, webhooks, email validation, do-not-contact lists

Primeforge (22 tools) - Workspaces, domains, mailboxes, DNS management, prewarmed mailboxes

Leadsforge (12 tools) - Contact search, email/phone/LinkedIn enrichment, lookalike search

Infraforge (24 tools) - Workspaces, domains, mailboxes, DNS, domain availability, credits

Warmforge (15 tools) - Workspaces, mailboxes, warmup stats, placement tests, latest mailbox placement results

Mailforge (23 tools) - Workspaces, domains, mailboxes, DNS management, domain availability, auto-renewal, domain masking, forwarding

Only provide API keys for the products you use. Tools for unconfigured products won't appear.

Related MCP server: Smartlead MCP Server

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "salesforge": {
      "url": "https://mcp.salesforge.ai/mcp",
      "headers": {
        "X-Salesforge-Key": "YOUR_SALESFORGE_API_KEY",
        "X-Primeforge-Key": "YOUR_PRIMEFORGE_API_KEY",
        "X-Leadsforge-Key": "YOUR_LEADSFORGE_API_KEY",
        "X-Infraforge-Key": "YOUR_INFRAFORGE_API_KEY",
        "X-Warmforge-Key": "YOUR_WARMFORGE_API_KEY",
        "X-Mailforge-Key": "YOUR_MAILFORGE_API_KEY"
      }
    }
  }
}

Remove header lines for products you don't use. Restart Claude Desktop after saving.

Claude Code

claude mcp add salesforge \
  --transport streamable-http \
  --url https://mcp.salesforge.ai/mcp \
  --header "X-Salesforge-Key: YOUR_SALESFORGE_API_KEY" \
  --header "X-Primeforge-Key: YOUR_PRIMEFORGE_API_KEY" \
  --header "X-Leadsforge-Key: YOUR_LEADSFORGE_API_KEY" \
  --header "X-Infraforge-Key: YOUR_INFRAFORGE_API_KEY" \
  --header "X-Warmforge-Key: YOUR_WARMFORGE_API_KEY" \
  --header "X-Mailforge-Key: YOUR_MAILFORGE_API_KEY"

Cursor

Go to Settings > MCP and add a new server:

• Name: salesforge

• Type: streamable-http

• URL: https://mcp.salesforge.ai/mcp

• Headers: same as above

Getting API Keys

Authentication Headers

Multiple Accounts

If you manage multiple accounts (for example, different clients), add separate server entries:

{
  "mcpServers": {
    "salesforge-client-a": {
      "url": "https://mcp.salesforge.ai/mcp",
      "headers": {
        "Authorization": "Bearer CLIENT_A_KEY"
      }
    },
    "salesforge-client-b": {
      "url": "https://mcp.salesforge.ai/mcp",
      "headers": {
        "Authorization": "Bearer CLIENT_B_KEY"
      }
    }
  }
}

Each entry gets its own name and API keys. Your AI assistant sees tools from both and you specify which client to work with in your prompts.

Usage Examples

After setup, try asking your AI assistant:

• "List my Salesforge workspaces"

• "Show contacts tagged with 'enterprise' in workspace X"

• "Create a new sequence called 'Q2 Outreach'"

• "Show the parent sequences and enrolled contacts for subsequence 31086"

• "Enroll these contacts into the sequence"

• "Show my Primeforge domains"

• "Search Leadsforge for CTOs at SaaS companies in New York"

• "Check my Infraforge credit balance"

• "Show warmup stats for my mailboxes"

• "Show which Warmforge mailboxes have 100% latest placement results"

• "List my Mailforge domains"

• "Check if example.com is available on Mailforge"

Project Structure

src/
├── index.ts              # stdio entry point
├── http.ts               # HTTP/SSE transport entry point
├── server.ts             # MCP server setup, tool registration
├── api-client.ts         # HTTP client for upstream APIs
├── client.ts             # legacy client
├── helpers.ts            # shared utilities
└── tools/
    ├── identity.ts       # API key validation
    ├── workspaces.ts     # workspace management
    ├── contacts.ts       # contact CRUD
    ├── mailboxes.ts      # mailbox and email operations
    ├── sequences.ts      # sequence lifecycle
    ├── subsequences.ts   # subsequence triggers, parents, and members
    ├── nodes.ts          # sequence node management
    ├── branches.ts       # sequence branches
    ├── enrollments.ts    # contact enrollment
    ├── linkedin.ts       # LinkedIn connection and authentication
    ├── tags.ts           # workspace tag discovery
    ├── sender-profiles.ts# sender profile management
    ├── validations.ts    # email validation
    ├── webhooks.ts       # webhook management
    ├── dnc.ts            # do-not-contact lists
    ├── custom-vars.ts    # custom variables
    ├── reference.ts      # action/condition type lookups
    ├── primeforge/       # domain, mailbox, workspace tools
    ├── leadsforge/       # search, enrichment, lookalike tools
    ├── infraforge/       # domain, mailbox, credit tools
    ├── warmforge/        # workspace, mailbox, placement test tools
    └── mailforge/        # workspace, domain, mailbox tools

Self-Hosting

If you prefer to run your own instance:

npm install
npm run build
npm run start:http

The server listens on port 3000 by default. API keys are passed as headers per request, not as environment variables.

The HTTP endpoint uses stateless MCP POST requests. Standalone SSE streams are not offered: GET /mcp (and HEAD) returns 405 Method Not Allowed before allocating an MCP server. Per-request servers and transports are closed after handling, on failures, and when clients disconnect before the response finishes.

Diagnostic logging

Logging is enabled by default as JSON lines on stderr, suitable for container log collection. MCP stdio output remains reserved for protocol messages. HTTP requests, including /health, receive a generated X-Request-Id response header that correlates their request and upstream API logs.

For more detail, run LOG_LEVEL=debug npm run start:http. Invalid settings fall back to their defaults. Keep info or debug enabled during timeout investigations so request starts and process metrics are retained.

• http.request.started without a matching completed or aborted event indicates an unfinished request or a process that stopped before logging completion. http.request.slow is emitted while the request is still pending, including during body parsing.

• upstream.request.slow identifies a pending product API call; its timing includes reading and parsing the response. The parent requestId links it to the HTTP request, and upstreamRequestId separates multiple API calls.

• runtime.metrics shows whether event-loop delay, CPU, memory, or request counts increased around a timeout. A blocked event loop also delays logging; its stall becomes visible after it resumes.

• If a timed-out health check has no corresponding request-start event, check proxy/load-balancer logs and container restarts too. Requests may not have reached Express, or the process may have been unable to run. Logging alone cannot establish the root cause.

The structured logs omit headers, bodies, query strings, upstream paths, and error messages/stacks to avoid capturing API keys and customer data. Errors include type, code, and HTTP status where available. Existing Node/Express native diagnostics may still appear separately. HTTP routes other than /health and /mcp are labeled other.

License

MIT

Salesforge account and contact management

These tools require the public API additions in multichannel-api #1068 and salesforge-api #2795 (SF-9461). The matching API changes must be deployed before the tools can be used.

To attach a standalone LinkedIn account, use create_sender_profile with its linkedinAccountId. The account must belong to the workspace and must not already be attached to another sender profile.

The existing delete_sender_profile tool also deletes its attached LinkedIn account.