Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Forge MCP Server List my Salesforge workspaces"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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 (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
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:
Name: salesforge
Type: streamable-http
Headers: same as above
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 |
|
|
Primeforge |
|
|
Leadsforge |
|
|
Infraforge |
|
|
Warmforge |
|
|
Mailforge |
|
|
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:
"List my Salesforge workspaces"
"Show contacts tagged with 'enterprise' in workspace X"
"Create a new sequence called 'Q2 Outreach'"
"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"
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
├── nodes.ts # sequence node management
├── branches.ts # sequence branches
├── enrollments.ts # contact enrollment
├── 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 toolsIf you prefer to run your own instance:
npm install
npm run build
npm run start:httpThe server listens on port 3000 by default. API keys are passed as headers per request, not as environment variables.
MIT
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Connect AI assistants to Stellary projects, boards, documents, and governed agent workflows.
Give AI agents the LinkedIn tools to find, qualify, engage, and follow up with prospects.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SalesforgeAI/forge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server