Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"salesforge": {
"url": "https://mcp.salesforge.ai/mcp",
"headers": {
"X-Mailforge-Key": "YOUR_MAILFORGE_API_KEY",
"X-Warmforge-Key": "YOUR_WARMFORGE_API_KEY",
"X-Infraforge-Key": "YOUR_INFRAFORGE_API_KEY",
"X-Leadsforge-Key": "YOUR_LEADSFORGE_API_KEY",
"X-Primeforge-Key": "YOUR_PRIMEFORGE_API_KEY",
"X-Salesforge-Key": "YOUR_SALESFORGE_API_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A remote MCP server that connects AI assistants to the full Salesforge product suite: Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be 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 marketing / communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
DataForSEO API modelcontextprotocol server
A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
PubNub Model Context Protocol MCP Server for Cursor and Claude
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 (13 tools) - 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.
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 A