Skip to main content

​
MCP — the Forest MCP server

The Forest MCP server exposes your Forest project to any Model Context Protocol client (Claude, IDE agents, your own tools). Where the forest plugin builds your back-office, MCP lets an agent operate on it — the same data and actions your team uses, through a governed interface.

​
What an agent can do

Read

List and search records, follow relationships, and read a single record.

Write

Create, update, and delete records, and associate/dissociate relationships.

Act

Run your collection’s Smart Actions — the same business operations exposed in the UI.

Understand

Describe collections, fields, and relationships so the agent can reason about your schema.

​
Governed by your permissions

The MCP server acts within Forest’s authorization model — an agent only sees and does what the authenticated scope is allowed to. Roles, scopes and permissions apply exactly as they do in the app, so exposing Forest over MCP doesn’t widen access.
Giving an agent write and action access to production data is powerful. Start against a non-production environment, and scope the agent to a role with the minimum permissions it needs.

​
Connecting

Add the Forest MCP server to your MCP client (for example, as a connector in Claude). It’s distributed as the forest-mcp plugin in the Forest Admin marketplace:
Setup specifics (authentication, selecting the project/environment) are covered by the forest-mcp plugin. This page describes what the server enables; follow the plugin for exact connection steps.

​
When to use MCP vs the plugin