FlowOn AI MCP Server
Overview
The FlowOn AI MCP Server is the bridge between AI assistants and the entire FlowOn for Dynamics. It exposes the full power of FlowOn Logic, FlowOn BPM, and Microsoft Dataverse as a set of intelligent tools that an AI agent can call autonomously to understand, design, build, and update your FlowOn configuration without requiring a developer or manual UI interaction.
Where FlowOn Logic empowers functional consultants to build solutions without code, the FlowOn AI MCP Server goes one step further: it empowers AI assistants to build those solutions on your behalf, following your instructions in natural language.
┌─────────────────────────────────────────────────────────────────────┐
│ FLOWON AI MCP SERVER AT A GLANCE │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ YOU SAY: │
│ ──────── │
│ "Create a validation logic block that checks the credit limit │
│ does not exceed the customer's tier maximum, and attach it │
│ to the Order entity on pre-create." │
│ │
│ THE AI DOES: │
│ ──────────── │
│ 1. Lists projects to find the right one │
│ 2. Reads Dataverse metadata to understand the Order entity │
│ 3. Creates a Validation Logic Block with the correct metadata │
│ 4. Verifies the result │
│ 5. Reports back with the new Logic Block ID │
│ │
│ WITHOUT: │
│ ───────── │
│ • Opening the FlowOn designer │
│ • Navigating menus │
│ • Writing any code │
│ • Manually looking up entity attributes │
│ │
└─────────────────────────────────────────────────────────────────────┘
Key Capabilities
| Capability | Description |
|---|---|
| Read | Query projects, solutions, logic blocks, flows, recipes, business processes, and Dataverse metadata |
| Create | Create new projects, logic blocks (all 5 types), and logic flows |
| Update | Modify the metadata of existing logic blocks and logic flows |
| Inspect | Explore full dependency graphs across all FlowOn artifacts |
| Publish | Trigger Dynamics 365 customization publishing after changes |
What is MCP?
Model Context Protocol (MCP) is an open standard that allows AI assistants (such as Claude, GitHub Copilot, and others) to interact with external tools and data sources in a structured, reliable way. Instead of an AI guessing how to interact with a system, MCP provides a formal contract: a defined set of tools with precise inputs, outputs, and descriptions.
The FlowOn AI MCP Server implements this protocol for the FlowOn for Dynamics platform. Once connected, an AI assistant can call any of the FlowOn MCP tools as part of completing a task you describe in natural language.
┌─────────────────────────────────────────────────────────────────────┐
│ HOW MCP FITS IN │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────┐ ┌──────────────────┐ ┌──────────┐ │
│ │ │ MCP │ FlowOn AI MCP │ SDK │ │ │
│ │ AI Agent │◄──────►│ Server │◄──────►│Dataverse │ │
│ │ (Claude, │ │ │ │ │ │
│ │ Copilot, │ │ • 30+ Tools │ │ FlowOn │ │
│ │ etc.) │ │ • Auth handled │ │ Logic │ │
│ │ │ │ • Error safety │ │ FlowOn │ │
│ └─────────────┘ └──────────────────┘ │ BPM │ │
│ └──────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────┘
Why This Matters
Without an MCP server, an AI assistant can only talk about FlowOn—it can suggest what a logic block might look like, but it cannot create it. With the FlowOn AI MCP Server connected, the AI assistant moves from advisor to actor. It can execute each step of a task end-to-end, verify the outcome after each step, and retry if something goes wrong.
How the MCP Server Works
The FlowOn AI MCP Server is a .NET application that:
- Connects to your Dataverse environment using the Microsoft Power Platform Dataverse Client
- Loads FlowOn project, logic, and BPM data into an in-memory store at startup
- Exposes a set of MCP tools that the AI can call to read and write FlowOn configuration
- Enforces business rules such as blocking modifications to managed solutions
┌─────────────────────────────────────────────────────────────────────┐
│ MCP SERVER INTERNAL ARCHITECTURE │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ MCP TOOLS LAYER │ │
│ │ │ │
│ │ ProjectTool SolutionTool LogicBlockTool LogicFlowTool │ │
│ │ LogicRecipeTool LogicBpmTool MetadataTool │ │
│ └──────────────────────────┬───────────────────────────────────┘ │
│ │ │
│ ┌──────────────────────────▼────────────────────────────────────┐ │
│ │ SERVICE LAYER │ │
│ │ │ │
│ │ IProjectService ILogicBlockStore ILogicFlowStore │ │
│ │ ILogicRecipeStore IBusinessProcessStore IMetadataRepository│ │
│ └──────────────────────────┬────────────────────────────────────┘ │
│ │ │
│ ┌──────────────────────────▼────────────────────────────────────┐ │
│ │ DATAVERSE CLIENT LAYER │ │
│ │ │ │
│ │ IOrganizationServiceAsync · IXrmService │ │
│ └───────────────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────┘
Product Scope
The MCP Server registers tools conditionally based on which FlowOn products are installed and licensed in the connected environment:
| MCP Tool Group | Required FlowOn Product |
|---|---|
| Project Tools | FlowOn Logic |
| Solution Tools | Dynamics 365 (always available) |
| Logic Block Tools | FlowOn Logic |
| Logic Flow Tools | FlowOn Logic |
| Logic Recipe Tools | FlowOn Logic |
| Business Process Tools | FlowOn BPM |
| Metadata Tools | Dynamics 365 (always available) |