MCP connections and Build Agent

  • Release version: Australia
  • Updated June 9, 2026
  • 2 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 (Model Context Protocol) connections enable the ServiceNow Build Agent to communicate seamlessly with external tools and resources through a standardized protocol. This integration facilitates accelerated and coordinated workflows by allowing AI agents to access third-party applications such as Figma, Atlassian, Zoom, and others without custom integration efforts. MCP serves as a unified communication layer that helps AI agents discover, invoke tools, and share context efficiently.

    Show full answer Show less

    Key Features

    • Supported MCP Connections: Build Agent currently supports MCP connections to multiple external systems including Atlassian, Rovo, Docusign, Figma, Linear, Miro, Prisma, Postgres, and various Zoom applications (Chat, Docs, Whiteboard).
    • Standardized Integration: MCP connectors in Connect Hub represent configured connections between ServiceNow and external MCP-compatible servers, enabling AI-driven, context-aware workflows.
    • Authentication and Activation: Initial manual authentication is required for each MCP connection before use with Build Agent. Administrators must approve MCP servers as AI assets in AI Control Tower, add them in Workflow Data Fabric, and users enable them in Build Agent settings.
    • Figma MCP Server: Provides a secure OAuth-based connection allowing Build Agent to access structured design data from Figma files. This enables faster, more accurate UI application development by translating Figma components, styles, and variables into machine-readable formats that Build Agent uses to generate code and design systems.
    • Usage in Development Environments: MCP connections are available in both ServiceNow Studio and ServiceNow IDE, requiring Australia Patch 3 or higher for Build Agent integration.

    Practical Application for ServiceNow Customers

    By configuring MCP connections, ServiceNow customers can extend Build Agent’s capabilities to automate and streamline workflows that involve third-party applications. For example, integration with Figma accelerates the design-to-development lifecycle by allowing Build Agent to directly convert design elements into application code, improving UI consistency and development speed.

    Before leveraging MCP connections, customers must ensure that:

    • Administrators add and approve MCP servers through Workflow Data Fabric and AI Control Tower.
    • Users authenticate and enable these MCP connections within Build Agent.

    This setup empowers Build Agent to operate cohesively across various systems, enhancing productivity and enabling more sophisticated, context-aware AI-assisted workflows.

    Next Steps for Implementation

    • Configure required MCP connections in Workflow Data Fabric following Model Context Protocol connector guidelines.
    • Obtain administrator approval for MCP servers in AI Control Tower.
    • Authenticate MCP connections via Personal Integrations.
    • Enable MCP servers within Build Agent settings to start using supported external tools.
    • For design-driven application development, connect the Figma MCP server to Build Agent to leverage design data securely and effectively.

    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:
    • Figma
    • Linear
    • Prisma Postgres
    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. For more information on MCP connections, see Additional connector configurations.

    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.

    For details on adding a new MCP connection in Workflow Data Fabric, see Model Context Protocol connectors.

    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 currently available only in the ServiceNow IDE, not ServiceNow Studio.

    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®.

    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.