# Flows MCP Server

Flows has a built-in MCP server, that lets your AI Assistant of choice build your flows for you.

Note

This MCP Server is different and separate to the custom MCP Servers you can **build** in Flows. See more for that [here](/core-blocks-reference/ai-blocks).

To configure the MCP server, point your AI Assistant at [https://mcp.useflows.eu](https://mcp.useflows.eu) or [https://mcp.useflows.us](https://mcp.useflows.us), depending on which instance you’re using, or [https://mcp.your.host](https://mcp.your.host) if on self-hosted.

It’s recommended to disable lazy tool loading when using the Flows MCP Server (if your AI Assistant has it enabled by default), and ensuring that the Assistant uses the `usage_instructions` tool, if it doesn’t on its own.

When connecting, you will be able to adjust AI Assistant access on a project-by-project basis, see [the oauth2 docs](/access-control/api-keys-and-oauth2) for more details.