Skip to main content
MCP (Model Context Protocol) is a standardized way to connect external tools, APIs, and data sources to Forest. Forest ships native connectors for popular tools, and lets you plug in any custom MCP server. MCP connectors are used inside workflows to trigger external actions, fetch data from external systems, and build multi-step processes that span several tools.

​
What is MCP?

The Model Context Protocol is an open standard for connecting AI assistants and applications to external tools and data sources. In Forest, an MCP connector exposes a third-party tool’s tools (its callable operations) so you can use them in your workflows. Each native connector wraps the tool’s official MCP server. Forest handles the connection and authentication, and the operations available are the ones that vendor’s MCP server exposes. For the exhaustive list of operations a connector provides, follow the vendor reference linked in each connector below.

​
Native MCP Connectors

Connect any of these from Project Settings → Integrations → Add MCP Server, then pick the connector instead of entering a URL.

​
Payments & billing

Stripe

Payments, customers, subscriptions, refunds.

Square

Payments, orders, catalog, customers.

​
CRM & support

HubSpot

Contacts, companies, deals, tickets.

Intercom

Conversations, contacts, articles.

Zendesk

Tickets, users, organizations.

​
Productivity & docs

Microsoft 365

Mail, calendar, files, Teams.

Notion

Pages, databases, search.

Monday.com

Boards, items, updates.

​
Communication

Slack

Messages, channels, users.

​
Analytics & data

Amplitude

Events, charts, cohorts.

Snowflake

Query tables and views.

​
Automation

n8n

Trigger and run n8n workflows.

Zapier

Trigger Zaps.

Workato

Trigger recipes.

​
Other

Kolar

Kolar operations.

Orias

Orias registry lookups.
The exact operations available come from each vendor’s MCP server and can change without notice, which is why Forest doesn’t duplicate the full tool list here. After connecting, the “Confirm the exposed tools” step shows you exactly what’s available for your account and plan.

​
Example: Stripe

Each native connector follows the same flow. For Stripe:
  1. Go to Project Settings → Integrations → Add MCP Server.
  2. Select Stripe.
  3. Complete the connector’s authentication.
  4. Confirm the exposed tools, then save.
What it unlocks: read and act on customers, charges, subscriptions, invoices and refunds from your workflows. For the full operation reference, see the Stripe MCP documentation.

​
Connect a custom MCP server

If a tool isn’t in the list above, connect any MCP server by URL:
  1. Navigate to Project Settings → Integrations.
  2. Click Add MCP Server.
  3. Enter your MCP server URL and configuration: 
    {
  "url": "https://your-mcp-server.com",
  "name": "My Custom MCP Server",
  "apiKey": "your-api-key"
}
  4. Check that all the expected tools are exposed.
  5. Save your configuration.
Learn more about building and hosting MCP servers in the Claude MCP documentation.