Forge Mcp
Wire your coding agent into the Salesforge cold-email and lead stack so you can manage outreach, infra, and mailboxes without leaving the IDE.
Overview
io.github.SalesforgeAI/forge-mcp is a Grow-phase MCP server that connects AI assistants to Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge through one stdio npm package.
What is this MCP server?
- Single MCP server spanning six Forge products: Salesforge, Primeforge, Leadsforge, Infraforge, Warmforge, and Mailforge
- stdio transport via npm package @salesforge/forge-mcp (v1.0.0)
- Per-product API keys from each app’s Settings > API (SALESFORGE, PRIMEFORGE, LEADSFORGE, INFRAFORGE, MAILFORGE)
- Agent-driven cold email, lead gen, and deliverability infra instead of juggling six browser tabs
- Covers 6 named Forge products in one server description
- Package version 1.0.0 on npm identifier @salesforge/forge-mcp
- Up to 5 documented secret API key environment variables
Community signal: 2 GitHub stars.
What problem does it solve?
Cold-email and lead infra sprawl across six Forge dashboards makes it painful to script campaigns or answer GTM questions from your agent without custom API glue.
Who is it for?
Indie SaaS founders running outbound on Salesforge who want agent-assisted campaign and infra tasks during growth.
Skip if: Builders with no Forge accounts, no outbound motion, or teams that need a full CRM replacement inside the agent.
What do I get? / Deliverables
After install, your agent can operate your Forge stack from one MCP config using product-specific API keys instead of manual dashboard work.
- Registered stdio MCP server pointing at @salesforge/forge-mcp
- Env vars for each Forge API key you enable
- Agent-callable tools across configured SalesforgeAI products
Recommended MCP Servers
Journey fit
Outbound sales and lifecycle automation sit in Grow once you are shipping and need repeatable pipeline motion, not in early build-only tooling. Lifecycle covers sequences, warming, and lead ops—the core jobs across Salesforge, Warmforge, Leadsforge, and Mailforge.
How it compares
First-party sales-stack MCP integration, not a generic REST skill or inbox-only email plugin.
Common Questions / FAQ
Who is io.github.SalesforgeAI/forge-mcp for?
Solo builders and small teams already on SalesforgeAI products who want Claude Code, Cursor, or Codex to manage outreach and related Forge services via MCP.
When should I use io.github.SalesforgeAI/forge-mcp?
Use it in the Grow phase when you are operating cold email, leads, warmup, or mail infra and want agent-driven actions instead of repetitive dashboard clicks.
How do I add io.github.SalesforgeAI/forge-mcp to my agent?
Add the @salesforge/forge-mcp npm package as a stdio MCP server in your client config and set SALESFORGE_API_KEY plus any other Forge API keys you use from each app’s Settings > API.