CommonFeaturesMCP Server
MCP Server

MCP Server

What is Model Context Protocol (MCP)?

Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to AI agents.

By connecting an agent to an MCP server, that server can offer tools and resources that give the agent the context it needs to solve a problem.

Flowgear exposes two MCP servers.

Workflow MCP Server

The Workflow MCP server allows published Flowgear Workflows to be exposed as MCP tools.

This works well for two broad categories of scenarios:

  • Utility workflows - perform a specific task such as approving a purchase order, listing service tickets or updating the status of a record.
  • Exploratory workflows - allow an AI agent to progressively find the data it needs by creating three MCP tool workflows - one to list available entities (e.g. tables), one to obtain the structure of an entity (e.g. fields) and one to run a query.

Read more about Workflow MCP Server (v2 Runtime) or MCP Tool Workflows (v1 Runtime).

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.

This is a powerful way to agentically build apps in your preferred IDE - frontend is created in your local repo while all interaction with your apps is mediated via Flowgear Workflows.

Read more about Builder MCP Server to see how to register the Builder MCP or dive in by using Builder MCP Server to create a Flowgear app.

Verify the MCP Endpoint

The Hostname shown against an Environment in the Console is the one you configured for it. That does not mean it is reachable yet. Flowgear provisions DNS and routing separately, so a saved Hostname can look correct in the Console while nothing resolves it.

An MCP client cannot reach Flowgear, or discover its OAuth configuration, while the Environment hostname is unavailable. Verify the endpoint before you register it with a client.

Open the URL for the MCP server you are configuring:

Workflow MCP: https://<environment-hostname>/mcp
Builder MCP:  https://<environment-hostname>/mcp/builder

<environment-hostname> is the complete hostname copied from the Console.

The endpoint is reachable when Flowgear returns a message identifying it as an MCP server URL:

  • Workflow MCP returns This is a Flowgear Workflow MCP server URL, not a web page.
  • Builder MCP returns This is a Flowgear Builder MCP server URL, not a web page.

Flowgear returns that message with the status 405 Method Not Allowed. The MCP endpoint expects an MCP client rather than a browser request, so the 405 is intentional. Seeing the Flowgear message is the successful result.

Check any other response against these cases:

  • DNS resolution, connection or certificate error - the hostname is not currently reachable.
  • A 404 or other non-Flowgear response - the selected MCP endpoint is not available for that hostname. Check that you used the Environment hostname rather than the Tenant hostname.
  • Your MCP client reports No authorization support detected - the client could not reach Flowgear to discover OAuth support. It does not mean that MCP is unavailable on your Flowgear plan. Flowgear MCP is currently available on all Flowgear plans.

Contact Flowgear Support to request or verify the DNS and routing setup for an Environment hostname.

See also

Read more