MCP connections and Build Agent

  • Release version: Australia
  • Updated July 21, 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 Build Agent in ServiceNow to securely and efficiently integrate with external third-party tools and resources using a standardized communication protocol called Model Context Protocol (MCP). This protocol allows AI agents to discover, invoke, and interact with external applications without custom integration development for each tool. MCP connections support coordinated workflows by exposing external tool capabilities directly to the Build Agent.

    Show full answer Show less

    Key Features

    • Supported MCP connections: Atlassian, Rovo, Docusign, Figma, Linear, Miro, Prisma, Postgres, Zoom (including Zoom Chat, Docs, and Whiteboard).
    • Zoom integration note: Each Zoom integration requires a separate app instance due to Build Agent’s single-server connection limitation.
    • Integration with Connect Hub: MCP connectors configured in Connect Hub represent approved and authenticated external MCP servers enabling AI agents to access their tools.
    • Authentication and approval workflow: Administrators must add MCP servers as Workflow Data Fabric connections, approve them as AI assets in AI Control Tower, and users must authenticate MCP connections before enabling them in Build Agent.
    • Viewing tools: Users can view available tools for each MCP server in the Build Agent settings panel (requires Australia Patch 5 or later).
    • Figma MCP server integration: Enables seamless translation of Figma design data into machine-readable format for Build Agent to generate enterprise-grade applications, accelerating design-to-development workflows.
    • Security: OAuth authentication is used for secure access to external systems like Figma.
    • Environment requirements: MCP connections are available in ServiceNow Studio and IDE, requiring Australia Patch 3 or higher for Build Agent MCP server support.

    Practical Application and Configuration

    ServiceNow customers can leverage MCP connections to automate and streamline workflows that involve multiple external applications, such as creating issues in Linear from tracked data or converting Figma UI designs directly into applications. Configuration involves:

    • Adding MCP servers as Workflow Data Fabric connections
    • Approving MCP servers as AI assets in AI Control Tower
    • Authenticating connections via Personal Integrations
    • Enabling MCP servers within Build Agent settings

    Note that MCP connections require manual authentication on first use and administrators must complete an approval process before enabling MCP servers for use.

    Benefits for ServiceNow Customers

    • Accelerated application development by integrating design tools like Figma directly into the Build Agent workflow.
    • Enhanced collaboration across multiple external systems using a standardized communication protocol.
    • Reduced need for custom integrations, lowering maintenance overhead and simplifying AI agent interactions.
    • Improved security and governance through administrator-controlled approvals and OAuth authentication.

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

    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 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: 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 Australia Patch 3 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.

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

    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
    MCP Servers panel listing enabled servers with Zoom Chat expanded to show available tools and descriptions.

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