MCP Server
Forest's MCP Server exposes your data, schemas, actions, and workflows to any MCP-compatible AI agent. Calls run under Forest's permissions and audit, inside your environment. Bring Claude, Cursor, or any custom runtime.

The same data backbone that powers the Forest backoffice is callable from external agents through the MCP server.
Runs inside your environment
Executed through the Forest Agent, behind your firewall. The MCP server does not push your data to Forest's cloud.
Permissions per agent
Each agent connects with a scoped role. It can read and act only within that scope, exactly like a human user.
Live data and schemas
Agents see your data live: tables, fields, relationships, computed values. Schema changes propagate automatically.
Same workflow surface
Agents can call the same Workflows and Actions humans run. The output of an agent step feeds back into the workflow.
Compatible MCP clients
Claude Desktop, Cursor, and any client supporting MCP. New clients connect through the standard protocol.
Unified audit
Every MCP call (read, action, workflow trigger) is logged the same way as a human action. The audit trail is one.


Built for agentic operations
Any MCP client
Claude Desktop, Cursor, custom runtimes. AI agents connect under scoped credentials and inherit your permission model.
Hybrid workflows
Your AI agents and your team work the same workflows, with handoffs between them recorded on the case.
Inside your perimeter
The MCP Server runs on the Forest backend, in your infrastructure. AI agents reach your data without it leaving your environment.
Vendor agnostic
Frequently asked questions
You still have question ?
Book a conversation with a forest expert
What is the Forest MCP Server?
It is Forest's implementation of the Model Context Protocol. It exposes your operational data, schemas, actions, and workflows to AI agents that speak MCP, under Forest's permission and audit model.
Where does it run?
Inside your infrastructure, through the Forest Agent. Data does not leave your environment to reach the MCP server.
Which clients can connect?
Any MCP-compatible client. Today that includes Claude Desktop, Cursor, and other emerging clients. The list grows as MCP adoption expands.
Are MCP calls audited?
Yes. Every call (data read, action invocation, workflow trigger) is recorded with the agent's identity, the input, the result, and any approval. The audit is at the record level.
Can an MCP agent run workflows?
Yes. Agents can trigger Workflows or take steps inside a running workflow, subject to their permissions. Workflow handoffs between agent and human work the same as in the Forest UI.
How is the MCP Server secured?
AI clients connect over OAuth and inherit the user's Forest roles and permissions: they can only do what that user could do through the UI. Every MCP call is logged like a human action. See MCP Server security.

