MCP server for Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-salesforgeai-forge-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for io.github.SalesforgeAI/forge-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
Salesforge (48 tools) - Workspaces, contacts, sequences, mailboxes, sender profiles, enrollments, 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 (12 tools) - Mailboxes, warmup stats, placement tests
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.
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 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"
Go to Settings > MCP and add a new server:
| Product | Where to get it |
|---|---|
| Salesforge | app.salesforge.ai > Settings > API |
| Primeforge | app.primeforge.ai > Settings > API |
| Leadsforge | app.leadsforge.ai > Settings > API |
| Infraforge | app.infraforge.ai > Settings > API |
| Warmforge | app.warmforge.ai > Settings > API |
| Mailforge | app.mailforge.ai > Settings > API |
| Product | Header | Format |
|---|---|---|
| Salesforge | X-Salesforge-Key | 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 |
| Mailforge | X-Mailforge-Key | YOUR_API_KEY |
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.
After setup, try asking your AI assistant: