MCP server
ForgeSend runs a Model Context Protocol (MCP) server, which lets an AI agent — like Claude or another MCP-compatible assistant — act on your ForgeSend workspace directly, instead of you clicking through the app yourself.
On this page
What is MCP
MCP is an open standard that lets an AI assistant call a defined set of tools against a real system — in this case, your ForgeSend workspace — rather than just talking about it. Once connected, an agent can list your campaigns, add contacts to a list, pull analytics, and more, using the same underlying actions the ForgeSend app itself uses.
Every action an MCP tool takes is scoped to the single workspace the connecting API key belongs to. An agent connected via MCP can't see or act on any other workspace.
Generating an API key
MCP clients authenticate with an API key, generated from Settings.
API Keys
Generate keys for external tools — like the MCP server — to access this workspace without a browser login.
Generating a key requires being a workspace owner. The full key is shown exactly once, immediately after generation — copy it right away, since it can't be displayed or recovered afterward, only revoked and replaced with a new one.
Give the key a descriptive label like "MCP server" so it's easy to identify — and revoke — later from the Active keys list without guessing which key is used where.
Configure your MCP client with that key as a bearer token against ForgeSend's MCP endpoint. Requests are rate-limited per workspace, so a single client behaving normally won't run into limits in everyday use.
The three tool categories
The MCP server exposes tools in three areas:
Campaign management
Create, update, schedule, pause/resume, and manage sequence steps
Lists / Contacts
View lists, add/update/search contacts, enroll contacts into a campaign
Analytics
Read-only — workspace analytics, per-campaign stats, daily send volume
- Campaign management — an agent can list your campaigns, create new ones, rename them, update their schedule, pause or resume sending, and add, edit, or remove sequence steps.
- Lists / Contacts — an agent can list your contact lists, add or update contacts, search contacts by name, email, or company, and add an entire list to a campaign as leads.
- Analytics — strictly read-only. An agent can pull workspace-wide analytics, per-campaign stats, and recent daily send volume, but has no tool that creates, changes, or deletes anything in Analytics.
What's intentionally not exposed
Enrichment and Find Leads have no MCP tools at all — an agent connected via MCP cannot run a lead search, enrich a contact, or spend enrichment credits in any way.
This is a deliberate boundary, not a gap to be filled later: Find Leads and Enrichment both spend real credits per action. Keeping them out of MCP protects against an agent unintentionally burning through your enrichment or lead-search balance on your behalf.
If you want an agent to work with newly found leads, the workflow is to run Find Leads yourself, then hand the resulting list to the agent — from there, its Lists/Contacts and Campaign management tools can take over.
Where to go next
Next: Getting started