--- sourceDocument: Zurich Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-development Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich 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: Zurich Updated July 21, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 ServiceNow Build Agent to securely access and integrate external tools and resources via standardized communication. This protocol allows AI agents within Build Agent to interact seamlessly with various third-party applications by discovering tools, invoking functions, and sharing context without custom integration coding. Show full answer Show less Build Agent currently supports MCP connections to multiple external systems, including Atlassian, Rovo, AWS DevOps, Box, Docusign, Figma, Linear, Miro, Prisma, Postgres, and several Zoom applications. Each Zoom integration requires a separate Zoom app due to server limitations. ## Key Features * **Standardized Integration:** MCP provides a uniform communication layer allowing Build Agent to connect with diverse third-party tools efficiently. * **Configurable Connectors:** In Connect Hub, MCP connectors represent configured, authenticated connections between ServiceNow and MCP-compatible external servers. * **Authentication and Approval:** Administrators must approve MCP servers as AI assets in AI Control Tower, add them as Workflow Data Fabric connections, and users must authenticate connections via Personal Integrations before enabling them in Build Agent settings. * **Tool Visibility:** Users can view available tools per MCP server within the Build Agent settings pane, provided the instance is on Australia Patch 5 or later. * **Support for Development Workflows:** For example, connecting the Figma MCP server enables Build Agent to access structured design data via OAuth, translating it into machine-readable formats to accelerate UI application development directly from Figma files. ## Practical Application for ServiceNow Customers By leveraging MCP connections, ServiceNow customers can automate and streamline workflows across systems and AI models without manual integration overhead. For instance, integrating Figma allows designers and developers to transition UI designs efficiently into functioning applications on the ServiceNow AI Platform, saving time and ensuring design consistency. Customers should ensure MCP servers are properly approved and authenticated following the outlined administrative process to enable and use these connections. The MCP connector setup enhances Build Agent's ability to coordinate tasks across platforms like Linear for issue tracking or Zoom for communication, improving productivity and collaboration. To connect Build Agent to MCP servers, users authenticate the connection once and then can invoke external tools through natural language prompts, enabling complex workflows such as creating projects or managing tasks across integrated services. ## Next Steps * Have administrators add and approve MCP servers in AI Control Tower and Workflow Data Fabric. * Authenticate MCP connections in Personal Integrations. * Enable the MCP servers in Build Agent settings to start using connected tools. * Contact Now Support to initiate allowlisting for connecting Build Agent to the Figma MCP server. 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__ul_hsb_hjc_cjc} Note: Because Build Agent doesn't support multiple servers connecting to one app, each Zoom integration requires its own app in Zoom. 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/47ZAF14eqLf9xYRyOF252w "Connect a supported MCP server to Build Agent to access external tools and resources in the chat panel when building and editing apps."). ## 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. 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, an administrator must approve it as an AI asset in AI Control Tower. Each MCP server requires this approval, regardless of whether the server is enabled by default. 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. The administrator approves the server as an AI asset in AI Control Tower. 3. You authenticate the connection in Personal Integrations. 4. You enable the MCP server in Build Agent settings. {#accelerate-design-to-development-with-figma-mcp-server__ol_scy_rw4_njc} Individual MCP servers are enabled by default, but the complete flow must be completed before any server is available for use. ## 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 enterprise-grade 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/6tcBL4f0l9z6adqqAeGkNw "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, rather than relying on static screen captures. With the available data, the Build Agent can effectively create 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 faster than with traditional approaches. The process of converting Figma designs to applications is as follows: * Designers use Figma to create user interface (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.