--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # MCP connections and Build Agent # MCP connections and Build Agent {#ariaid-title1} Release version: Australia Updated October 20, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of MCP connections and Build Agent MCP (Model Context Protocol) connections enable the Build Agent in ServiceNow to securely integrate with external third-party tools and resources through a standardized communication protocol. This allows seamless interaction between AI agents and external applications, facilitating coordinated workflows without the need for custom integration for each tool. MCP connections are essential for accelerating processes such as design-to-development workflows by connecting Build Agent to applications like Figma, Atlassian, AWS, Zoom, and more. Show full answer Show less ## Supported MCP Connections Build Agent currently supports MCP connections with several popular platforms including Atlassian, Rovo, AWS DevOps, Box, Docusign, Figma, Linear, Miro, Prisma, Postgres, and Zoom (including Zoom Chat, Docs, and Whiteboard). Each Zoom integration requires a separate app in Zoom due to Build Agent's limitation of not supporting multiple servers connecting to one app. ## Key Configuration and Usage Details * Custom MCP servers can be created on the ServiceNow AI Platform and connected to Build Agent. * Each MCP server must be approved as an AI asset by a user with the `snaigovernance.aisteward` role via AI Control Tower before use. * The approval and activation process involves adding the server as a Workflow Data Fabric connection, approval in AI Control Tower, personal authentication, and enabling the server in Build Agent settings. * Connecting to MCP servers requires manual authentication the first time in Build Agent. * Users can view available tools per MCP server in the Build Agent settings panel starting from Australia Patch 5. ## Figma MCP Server Integration The Figma MCP server provides a secure OAuth-authenticated connection between Build Agent and Figma, allowing Build Agent to access structured design data such as components, styles, and variables directly from Figma files. This enables automated and accurate generation of application user interfaces based on live design data rather than static images. * Designers create UI components in Figma. * The Figma MCP server converts design data into a machine-readable format. * Build Agent uses this data to generate applications on the ServiceNow AI Platform. Note that connecting Build Agent to the Figma MCP server requires an allowlist process initiated through Now Support. ## Practical Benefits for ServiceNow Customers * Accelerate application development by integrating design and development workflows. * Enable AI-driven automation and tool interoperability across multiple third-party platforms. * Maintain secure, governed connections with external systems through controlled approval and authentication processes. * Utilize a standardized protocol to reduce custom integration overhead and streamline the addition of new tools. MCP connections enable Build Agent to access external tools and resources through standardized communication. Use these connections to integrate third-party applications like Figma for accelerated design-to-development workflows. The following MCP connections are currently supported for Build Agent: * Atlassian Rovo * AWS DevOps * Box * Docusign * Figma * Linear * Miro * Prisma Postgres * Zoom * Zoom Chat * Zoom Docs * Zoom Whiteboard {#accelerate-design-to-development-with-figma-mcp-server__ba-ae-mcp-servers-supported} Note: Because Build Agent doesn't support multiple servers connecting to one app, each Zoom integration requires its own app in Zoom. You can create custom MCP servers on the ServiceNow AI Platform and then have Build Agent connect to them. For information about creating custom MCP servers, see [Create a Model Context Protocol server](https://www.servicenow.com/docs/access?context=create-mcp-server&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US). MCP is an open protocol that defines how AI agents communicate with external systems to discover and invoke tools, retrieve resources, and share context. By standardizing this communication layer, MCP enables AI agents to interact with a wide range of third-party applications without requiring custom integration logic for each one. In Connect Hub, an MCP connector represents a configured connection between ServiceNow and an external system that exposes a server compatible with MCP. After you set up an MCP connector, AI agents can use it to access tools and capabilities from the external system, enabling coordinated workflows across models and systems. ## Configuration details {#accelerate-design-to-development-with-figma-mcp-server__section_u2z_zgq_z3c2} For details on configuring MCP connections in Build Agent, see [Connect Build Agent to a supported MCP server](https://www.servicenow.com/docs/a7jVLFOgqGPLT0iMDDiSRQ "Connect a supported MCP server to Build Agent to access external tools and resources in the chat panel when building and editing apps."). For more information on MCP connections, see [Additional connector configurations](https://www.servicenow.com/docs/access?context=additional-configs-mcr&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). ## Connect to supported MCP servers {#accelerate-design-to-development-with-figma-mcp-server__section_iq3_jfq_z3c} Build Agent can use any MCP connection that's available in an instance's registry, though you must manually authenticate the connection the first time you use it with Build Agent. For details on adding a new MCP connection in Workflow Data Fabric, see [Model Context Protocol connectors](https://www.servicenow.com/docs/access?context=model-context-protocol-connector&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). An example prompt: Let's create a new project to track my baby's sleep and create issues in Linear based on inputs from the tracker. Note: MCP connections are available in both ServiceNow Studio and the ServiceNow IDE. ## Approve and activate MCP servers {#accelerate-design-to-development-with-figma-mcp-server__section_mcp_governance} Before you can enable an MCP server in Build Agent, a user with the sn_ai_governance.ai_steward role must approve it as an AI asset in AI Control Tower. An administrator without this role can't approve the server. Each MCP server requires this approval, regardless of whether the server is enabled by default. For the approval steps, see [Onboard MCP server approval playbook](https://www.servicenow.com/docs/access?context=aict-onboard-mcp-server-approval-playbook&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US). The end-to-end flow for making an MCP server available is: 1. The administrator adds the MCP server as a Workflow Data Fabric (WDF) connection. 2. A user with the sn_ai_governance.ai_steward role approves the server as an AI asset in AI Control Tower. 3. You authenticate the connection in Personal Integrations. For details, see [Using the Personal Authentication dashboard](https://www.servicenow.com/docs/access?context=personal-auth-dashboard&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). 4. You enable the MCP server in Build Agent settings. {#accelerate-design-to-development-with-figma-mcp-server__ol_scy_rw4_njc}For details on adding the MCP server connection, see the following topics: * [Dynamic client registration](https://www.servicenow.com/docs/access?context=mcp-dcr-a&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) for servers that connect with one click * [Manual client registration](https://www.servicenow.com/docs/access?context=mcp-mcr-a&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) for servers marked Manual setup may be required * [Client registration using custom connector](https://www.servicenow.com/docs/access?context=mcp-custom&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) for servers that aren't in the MCP registry {#accelerate-design-to-development-with-figma-mcp-server__ul_ba_mcp_registration_1} Individual MCP servers are enabled by default, but the complete flow must be completed before any server is available for use. For details on adding a new MCP connection in Workflow Data Fabric, see [Model Context Protocol connectors](https://www.servicenow.com/docs/access?context=model-context-protocol-connector&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). ## View available tools per MCP server {#accelerate-design-to-development-with-figma-mcp-server__view-available-tools-per-mcp-server} You can view the list of tools available for each connected MCP server in the MCP servers pane in the Build Agent settings panel. Expand a server by selecting the chevron next to the server name to see its tools and descriptions. Note: You must be on Australia Patch 5 or later to view MCP tools. Figure 1. MCP tools list ## Application development with Figma MCP server {#accelerate-design-to-development-with-figma-mcp-server__section_kwd_l42_dhc} Connect the Figma MCP server to the Build Agent to accelerate the transition of your Figma designs to applications on the ServiceNow AI Platform®. Note: You can upload additional types of files to accelerate development, such as images and code files. For more information, see [Supported file types for Build Agent](https://www.servicenow.com/docs/UURCsFI~iOs9Vhaw2FanrA "Build Agent accepts images, documents, code files, and file types specific to ServiceNow as uploads. Supported formats, size limits, and general guidelines apply when generating apps and metadata."). The Figma MCP (Model Context Protocol) server establishes a secure connection between the Build Agent and Figma using OAuth for login authentication. This server enables the Build Agent to access structured design data directly from Figma files, instead of using static screen captures. With the available data, the Build Agent can generate applications. The Figma MCP server translates Figma data, such as components, styles, and variables, into a machine-readable format. The Build Agent uses the translated data to generate code, gather design context, or develop design systems directly from Figma. Developers can create more accurate and consistent application UIs (user interfaces). The process of converting Figma designs to applications is as follows: * Designers use Figma to create UI components, styles, and variables. * The Figma MCP server uses OAuth to securely access design data from Figma. * The Figma MCP server acts as an intermediary, converting Figma design data into the Build Agent context. * The Build Agent, which is installed on your ServiceNow® instance, receives the translated data and uses it to generate applications. * The Build Agent creates applications based on the design data provided by Figma. {#accelerate-design-to-development-with-figma-mcp-server__ul_isw_1q2_dhc} Note: An allowlist process is required to connect the Build Agent MCP client to the Figma MCP server. Contact Now Support to initiate the process.