MCP connections and Build Agent

  • Release version: Zurich
  • Updated June 23, 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 (Model Context Protocol) connections enable the Build Agent in ServiceNow to securely and efficiently integrate with external third-party tools and resources through a standardized communication protocol. This integration allows AI agents to discover, invoke tools, retrieve resources, and share context across multiple systems without needing custom integration for each application. MCP connections support tools like Figma, Atlassian, Zoom, Linear, and more, enhancing workflows such as design-to-development pipelines.

    Show full answer Show less

    Key Features

    • Standardized Communication: MCP enables AI agents to interact with various external applications via a common protocol, simplifying integration and coordination.
    • Supported Connections: Build Agent currently supports MCP connections for Atlassian, Rovo, Docusign, Figma, Linear, Miro, Prisma, Postgres, Zoom (including Zoom Chat, Docs, Whiteboard).
    • Zoom Integration Note: Each Zoom integration requires a dedicated app, as Build Agent does not support multiple servers connecting to a single app.
    • Authentication & Approval: Administrators must approve MCP servers as AI assets in AI Control Tower. Users authenticate connections via Personal Integrations before enabling MCP servers in Build Agent.
    • Configuration: MCP connectors are configured in Connect Hub and must be manually authenticated the first time they’re used with Build Agent. MCP connections are accessible in both ServiceNow Studio and ServiceNow IDE (Zurich Patch 10+ required for Studio).

    Application Development with Figma MCP Server

    • Accelerated Design-to-Development: The Figma MCP server facilitates direct access to structured design data (components, styles, variables) from Figma via OAuth authentication, enabling Build Agent to generate accurate and consistent application UIs faster.
    • Data Translation: Figma design data is converted into a machine-readable format usable by the Build Agent to create applications aligned with the design context.
    • Supported File Types: Besides Figma files, additional files such as images and code files can be uploaded to further accelerate development.
    • Security & Access: An allowlist process managed by Now Support is required to connect the Build Agent MCP client to the Figma MCP server, ensuring secure and authorized integration.

    Practical Benefits for ServiceNow Customers

    • Enables seamless integration of AI-powered Build Agent workflows with popular third-party applications, reducing development time and manual effort.
    • Provides enhanced coordination and context sharing across tools, supporting more efficient and accurate application creation.
    • Allows administrators to control and approve integrations securely through AI Control Tower and Workflow Data Fabric connections.
    • Facilitates accelerated UI development by leveraging design data directly from Figma, improving consistency and reducing rework.

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

    Configuration details

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