
The Forge MCP Server connects your Salesforge product suite to any AI assistant that supports the Model Context Protocol (MCP). This includes Claude, Cursor, Windsurf, and other MCP-compatible tools.
Once connected, you can manage your outreach workflow through natural conversation: list workspaces, create contacts, launch sequences, check analytics, and more.
MCP is an open standard developed by Anthropic that allows AI assistants to interact with external services securely. Your API key stays on your machine and is only used to authenticate requests.
The MCP server supports all Salesforge products through a single endpoint:
Salesforge - Workspaces, contacts, sequences, mailboxes, sender profiles, enrollments, webhooks, email validation, do-not-contact lists
Primeforge - Workspaces, domains, mailboxes, DNS management, prewarmed mailboxes
Leadsforge - Contact search, email/phone/LinkedIn enrichment, lookalike search
Infraforge - Workspaces, domains, mailboxes, DNS, domain availability, credits
Warmforge - Mailboxes, warmup stats, placement tests
You only need API keys for the products you use. Tools for unconfigured products will not appear.
An account on one or more Salesforge products with API access
An MCP-compatible AI client (Claude Desktop, Claude Code, Cursor, Windsurf, etc.)
Generate API keys for each product you want to connect:
Salesforge: Log in at app.salesforge.ai, go to Settings > API, click Generate API Key
Primeforge: Log in at app.primeforge.ai, go to Settings > API, click Generate API Key
Leadsforge: Log in at app.leadsforge.ai, go to Settings > API, click Generate API Key
Infraforge: Log in at app.infraforge.ai, go to Settings > API, click Generate API Key
Warmforge: Log in at app.warmforge.ai, go to Settings > API, click Generate API Key
Copy each key and store it somewhere safe. You will need them in the next step.
Open Claude Desktop
Go to Settings > Developer > Edit Config
This opens the claude_desktop_config.json file. Add the following configuration:
{
"mcpServers": {
"salesforge": {
"url": "https://mcp.salesforge.ai/mcp",
"headers": {
"Authorization": "Bearer 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"
}
}
}
}Replace each YOUR_..._API_KEY placeholder with the key you generated in Step 1. Remove any header lines for products you do not use.
Save the file and restart Claude Desktop.
If you use Claude Code (the CLI tool), add the server to your project or global settings:
claude mcp add salesforge \
--transport streamable-http \
--url https://mcp.salesforge.ai/mcp \
--header "Authorization: Bearer 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"Only include the headers for products you have API keys for.
If you use Cursor, go to Settings > MCP and add a new server with these details:
Name: salesforge
Type: streamable-http
URL: https://mcp.salesforge.ai/mcp
Headers: Add the same headers as above for each product you use
After setup, try asking your AI assistant:
"List my Salesforge workspaces"
"Show my Primeforge domains"
"What is my Leadsforge credit balance?"
"List my Infraforge mailboxes"
"Show my Warmforge warmup stats"
If the connection is working, you will see data from your account.
ProductHeaderFormat | ||
Salesforge | Authorization | Bearer YOUR_API_KEY |
Primeforge | X-Primeforge-Key | YOUR_API_KEY |
Leadsforge | X-Leadsforge-Key | YOUR_API_KEY |
Infraforge | X-Infraforge-Key | YOUR_API_KEY |
Warmforge | X-Warmforge-Key | YOUR_API_KEY |
Tools not showing up: Make sure you restarted your AI client after editing the config. Verify the API key is correct.
Authentication errors: Double-check the API key. Salesforge uses "Bearer" prefix in the Authorization header; other products use raw keys in custom headers.
"Invalid workspace" errors: Some tools require a workspace ID. Use the list workspaces tool first to get valid IDs.
Missing product tools: Tools only appear for products where you have provided a valid API key.