Forge API & MCP: Rate Limits, Authentication & Known Gaps

This article covers the current rate limits, authentication requirements, API documentation, and known limitations across the Forge APIs and MCP tools.

1. API rate limits

Rate limits vary between Forge products.

Leadsforge

The following limits currently apply:

• Search and search-count requests: 20 requests per minute

• Enrichment job status and results: 60 requests per minute

• Maximum of 500 contacts per enrichment batch

Primeforge

• No API rate limit is currently enforced.

Multichannel

• No API rate limit is currently enforced.

Salesforge

• No API rate limit is currently enforced on the public API.

Infraforge

• No API rate limit is currently enforced.

Warmforge

Warmforge uses endpoint-specific limits:

• Most mailbox and placement-test GET requests: 100 requests per minute

• SMTP/OAuth2 connection requests: 10 requests per minute

• Placement-test creation: 10 requests per minute

• Mailbox bulk updates currently have no rate limit

These limits may change as the APIs evolve.

2. MCP authentication

MCP uses product-specific API keys for authentication.

The following headers are used:

• Salesforge: X-Salesforge-Key

• Primeforge: X-Primeforge-Key

• Leadsforge: X-Leadsforge-Key

• Infraforge: X-Infraforge-Key

• Warmforge: X-Warmforge-Key

• Mailforge: X-Mailforge-Key

Only configure the headers for the Forge products you are using.

Export authentication

Mailbox exports are an exception to the normal MCP authentication pattern.

All public API mailbox exports require:

• The normal API-key authentication header

• The account email address in the request body

• The account password in the request body

This applies to exports to:

• Salesforge

• Warmforge

• Instantly

• Smartlead

• EmailBison

• Lemlist

• Reply.io

• Snov.io

• Woodpecker

Some export destinations have additional requirements:

• EmailBison also requires appUrl and clientId

• Lemlist requires an additional OTP/magic-link verification step

The email and password requirements do not replace the API key. They are required in addition to it for export operations.

3. Known MCP limitations

MCP functionality is still being expanded. The following features are currently not supported through MCP.

Creating sender profiles

There is currently no create_sender_profile MCP tool.

Sender profiles can be listed, updated, deleted, and assigned, but they cannot currently be created through MCP.

An implementation is currently in progress. This article will be updated once the functionality is available.

Updating dailyEmailLimit

The underlying public API supports updating a mailbox's dailyEmailLimit, but this is not currently supported through MCP.

Tag-name filters in list_contacts

list_contacts currently supports filtering by tag IDs, but tag names are not supported as filters.

If a tag name is provided instead of the tag ID, the filter will not be applied as expected.

Tag-name filters in enroll_contacts

enroll_contacts has the same limitation.

Tag-name filters are not currently supported. Use tag IDs instead.

An implementation to address the tag filtering limitations is currently in progress. This article will be updated once the changes are available.

4. API documentation

Each Forge product has its own API documentation and Swagger/OpenAPI reference.

Use the documentation for the product you are integrating with:

• Salesforge/multichannel API

• Primeforge API

• Leadsforge API

• Infraforge API

• Warmforge API

• Mailforge API

The API endpoints and authentication methods can differ between products, so make sure you are using the documentation for the correct API.

5. Keeping this information up to date

Forge APIs and MCP tools are actively being developed, so features listed as unsupported may become available over time.

We will update this article when:

• New MCP functionality becomes available

• Existing MCP limitations are resolved

• API rate limits change

• Authentication requirements change

For MCP setup instructions, see the Forge MCP Server article.