MCP connections and Build Agent

  • Release version: Zurich
  • Updated June 9, 2026
  • 3 minutes to read
    • Summarize
    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 connections enable the ServiceNow Build Agent to securely and efficiently access external tools and resources through a standardized communication protocol called Model Context Protocol (MCP). This allows seamless integration with a variety of third-party applications such as Figma, Atlassian, Zoom, and others, facilitating coordinated, context-aware workflows that accelerate development processes.

    Show full answer Show less

    MCP standardizes how AI agents communicate with external systems to discover tools, retrieve resources, and share context without requiring custom integration logic. Within ServiceNow’s Connect Hub, MCP connectors represent configured connections between ServiceNow and MCP-compatible external systems, enabling Build Agent to leverage those systems’ capabilities.

    Key Features

    • Supported MCP Connections for Build Agent: Includes Atlassian, Rovo, Docusign, Figma, Linear, Miro, Prisma, Postgres, Zoom (with special considerations for multiple instances), Zoom Chat, Zoom Docs, and Zoom Whiteboard.
    • Authentication and Authorization: Each MCP connection requires manual authentication for the first use, and an administrator must approve each MCP server as an AI asset in AI Control Tower before it can be enabled for Build Agent.
    • Integration Workflow: The process involves adding the MCP server as a Workflow Data Fabric connection, admin approval in AI Control Tower, user authentication via Personal Integrations, and enabling the server in Build Agent settings.
    • Development Acceleration with Figma MCP Server: The Figma MCP server uses OAuth for secure access to structured design data (components, styles, variables) directly from Figma files. This enables Build Agent to transform design data into machine-readable formats, facilitating rapid, accurate creation of enterprise-grade applications with consistent UI.
    • Environment Requirements: MCP connections are accessible in both ServiceNow Studio and the ServiceNow IDE, with the requirement of Zurich Patch 10 or higher for Studio.

    Practical Benefits for ServiceNow Customers

    • Leverage existing design and collaboration tools to streamline the design-to-development lifecycle, reducing manual translation efforts.
    • Enable AI-driven Build Agent workflows that interact seamlessly with multiple third-party applications, improving productivity and consistency across projects.
    • Securely manage and approve MCP connections to maintain control over external integrations and data access within the ServiceNow environment.
    • Accelerate application development by directly using structured design data from Figma, minimizing errors and rework in UI creation.

    Next Steps

    • Have administrators add and approve MCP servers via Workflow Data Fabric and AI Control Tower.
    • Authenticate MCP connections through Personal Integrations and enable them in Build Agent settings.
    • Configure Figma MCP server integration to utilize design data for faster application creation.
    • Refer to ServiceNow documentation for detailed configuration guidance on connecting Build Agent to MCP servers.

    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
    • Docusign
    • Figma
    • Linear
    • Miro
    • Prisma Postgres
    • Zoom
    • Zoom Chat
    • Zoom Docs
    • Zoom Whiteboard
    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 allows 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. Once an MCP connector is set up, AI agents can use it to access the tools and capabilities that the external system provides, enabling coordinated, context-aware workflows across models and systems.

    For details on configuring MCP connections in Build Agent, see Connect Build Agent to a supported MCP server.

    Connect to supported MCP servers

    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 want to use it with Build Agent.

    An example prompt could be something like the following: 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, though you must be on Zurich Patch 10 or higher to use MPC servers with Build Agent in ServiceNow Studio.

    Approve and activate MCP servers

    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.

    Individual MCP servers are enabled by default, but the complete flow must be completed before any server is available for use.

    Application development with Figma MCP server

    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.

    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. Consequently, 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 employs OAuth to securely access design data from Figma.
    • The Figma MCP server acts as an intermediary, converting Figma’s 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.
    For configuration information, see Connect Build Agent to a Figma MCP server.