Builder MCP Server

The Builder MCP server exposes the same Workflow-building tool surface used by Flowgear's built-in tooling so that Workflows can be created and tested from outside the Console.

For most people, the easiest way to work with Builder MCP is from an IDE or editor. You keep the frontend in your local repository, and use Flowgear Workflows as the backend. If you prefer a more terminal-first or graphical way of working, Builder MCP can also work there when the client supports it.

Set up the Builder MCP Server

The best way to get started is to use the Builder MCP Server to create a Flowgear app.

These steps apply to every client. The client sections below cover only what is specific to each one.

Target a test Environment. Builder Tools create and change Workflows, so don't point a client at a production Environment.
Use this Builder MCP URL:
```
https://<environment-hostname>/mcp/builder
```
<environment-hostname> is the complete hostname of the Environment you want to target, copied from the Console.
Open that URL in a browser before you register it, and confirm that Flowgear displays its Builder MCP server guidance. See how to Verify the MCP Endpoint.
Complete Flowgear OAuth when the client prompts you. Each client starts the browser sign-in flow in its own way.
Load Builder Guidance once. Prefer the flowgear://builder/guidance Resource, which capable clients read on their own. If your client can't read MCP Resources, call GetBuilderGuidance once instead.
Call GetBuilderContext before you make any changes. It returns the tenant, Site, and Environment behind the current connection, so you can confirm you're working against the right target.

Builder MCP involves a large number of Tool calls. Review your client's approval or permission settings before you start, and only relax them in a development environment.

Use flowgear as the server name in all commands. This must stay flowgear because the sample app's agents.md expects that name.

Choose your Client

OpenAI Codex

Install and sign in to Codex using the Codex CLI documentation, then register the Builder MCP Server:

codex mcp add flowgear --url https://<environment-hostname>/mcp/builder

codex mcp add starts the OAuth flow when it detects one. If it doesn't start, run codex mcp login flowgear.

Codex reads the flowgear://builder/guidance Resource on its own, so you don't need to call GetBuilderGuidance.

Anthropic Claude Code

Install and sign in to Claude Code using the Claude Code Quickstart, then register the Builder MCP Server:

claude mcp add --transport http flowgear https://<environment-hostname>/mcp/builder

Run /mcp in Claude Code, then select Authenticate for flowgear to complete the Flowgear sign-in flow.

Claude Code reads the flowgear://builder/guidance Resource on its own, so you don't need to call GetBuilderGuidance.

GitHub Copilot

GitHub Copilot is a separate product from Microsoft Copilot. If you're looking for Microsoft Copilot Studio or the Microsoft 365 Copilot app, see Microsoft Copilot below.

GitHub Copilot CLI

Install and sign in to Copilot CLI using Installing GitHub Copilot CLI, then register the Builder MCP Server:

copilot mcp add --transport http flowgear https://<environment-hostname>/mcp/builder

Start every Builder session with the MCP server instructions flag:

copilot --allow-all-mcp-server-instructions

Copilot CLI doesn't apply Builder MCP server instructions without this flag. The flag covers one session, so supply it each time you start Copilot CLI.

During Flowgear testing, Copilot CLI exposed Builder MCP Tools but not MCP Resources, so ensure GetBuilderGuidance is called once at the start of a session.

GitHub Copilot for Visual Studio Code

Copilot ships with Visual Studio Code. See MCP Servers in Visual Studio Code for how to add and start a server, then add the Flowgear server to your MCP configuration:

{
  "servers": {
    "flowgear": {
      "type": "http",
      "url": "https://<environment-hostname>/mcp/builder"
    }
  }
}

Visual Studio Code supports MCP Resources, but Builder Guidance did not load on its own during Flowgear testing, so ensure GetBuilderGuidance is called when the guidance is missing.

GitHub Copilot App

Add the Flowgear server under MCP Servers in the app settings. See Customize the GitHub Copilot App.

During Flowgear testing, connection, OAuth, Tool discovery, and Tool calls all worked. Server instructions and Builder Guidance were not applied consistently, and the app has no equivalent of the Copilot CLI instructions flag, so ensure GetBuilderGuidance is called at the start of a session. Copilot CLI and Copilot for Visual Studio Code gave more consistent results.

Microsoft Copilot

Microsoft Copilot is a separate product from GitHub Copilot. If you're looking for the Copilot CLI, Copilot in Visual Studio Code, or the GitHub Copilot app, see GitHub Copilot above.

Microsoft Copilot Studio

Copilot Studio gave the most consistent Microsoft Copilot result during Flowgear testing. It runs as a managed agent rather than a coding client, so it can't see your repository.

Follow Connect a Copilot Studio Agent to an MCP Server to add the Builder MCP URL to an agent. Select OAuth 2.0 as the authentication type and Dynamic discovery as the type, create the MCP connection, then complete Flowgear authentication.

Copilot Studio doesn't apply Builder Guidance on its own. Load it into the agent instead:

Call GetBuilderGuidance from a test conversation.
Copy the full text it returns into the agent's Instructions.
Save the agent, then start a new test conversation.

The guidance will now apply to every conversation with the agent. The copied text is a snapshot, so refresh it after a major change to Builder Guidance.

Microsoft 365 Copilot App

The Microsoft 365 Copilot app is where people usually consume a Copilot Studio agent that has already been published. You configure the Builder MCP URL in Copilot Studio, not in the Microsoft 365 Copilot app.

See Microsoft 365 Copilot App Overview.

Other Clients

You can also use the Builder MCP Server with other MCP clients, as long as the client supports MCP Tools.

Specifically, the client must support:

Remote HTTP MCP servers.
OAuth 2.0 authentication flows.

An example of a client that currently documents these MCP capabilities is Gemini CLI MCP.