---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Connect to supported MCP servers

# Connect Build Agent to a supported MCP server {#ariaid-title1}

Release version: Australia  
Updated October 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Connect a supported MCP server to Build Agent to access external tools and resources in the chat panel when building and editing apps.

## Before you begin

Before you can enable an MCP server in Build Agent, a user with the sn_ai_governance.ai_steward role must approve it as an AI asset in AI Control Tower. An administrator without this role can't approve the server. Each MCP server requires this approval, regardless of whether the server is enabled by default. For the approval steps, see [Onboard MCP server approval playbook](https://www.servicenow.com/docs/access?context=aict-onboard-mcp-server-approval-playbook&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US).

You must have Connect Hub installed.  
Note:  
MCP settings currently apply to Build Agent, not Autonomous Engineer.  
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. A user with the sn_ai_governance.ai_steward role approves the server as an AI asset in AI Control Tower.
3. You authenticate the connection in Personal Integrations. For details, see [Using the Personal Authentication dashboard](https://www.servicenow.com/docs/access?context=personal-auth-dashboard&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).
4. You enable the MCP server in Build Agent settings.

{#ba-connct-mcp-server__ol_scy_rw4_njc}For details on adding the MCP server connection, see the following topics:

* [Dynamic client registration](https://www.servicenow.com/docs/access?context=mcp-dcr-a&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) for servers that connect with one click
* [Manual client registration](https://www.servicenow.com/docs/access?context=mcp-mcr-a&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) for servers marked Manual setup may be required
* [Client registration using custom connector](https://www.servicenow.com/docs/access?context=mcp-custom&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) for servers that aren't in the MCP registry
{#ba-connct-mcp-server__ul_ba_mcp_registration_1}  
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.

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](https://www.servicenow.com/docs/access?context=model-context-protocol-connector&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).

See [MCP connections and Build Agent](https://www.servicenow.com/docs/fyp9sEVcF_WfN6bg9btgKw "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.") for a list of supported MCP servers.  
Note:  
MCP connections are available in both ServiceNow Studio and the ServiceNow IDE.

Role required: admin

## Procedure

1. Navigate to AllApp DevelopmentServiceNow Studio or AllApp DevelopmentServiceNow IDE.
2. Select the Settings icon ![]() in the Build Agent chat panel.  
   Figure 1. Build Agent panel with Settings icon
3. Select the Enable MCP servers toggle on the MCP tab.
4. Select the MCP server to enable.  
   Figure 2. Enable MCP servers setting  
   Note:  
   If the MCP server isn't available, authenticate the connection first. Navigate to AllIntegrationHubPersonal AuthenticationPersonal Integrations. This task requires the sn_personal_auth.personal_auth_user role. For more information, see [Using the Personal Authentication dashboard](https://www.servicenow.com/docs/access?context=personal-auth-dashboard&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).
5. Select Allow in the confirmation dialog.  
   You must do this only for the initial connection.
6. **Optional:** View the list of available tools that you can call for each MCP server by expanding the server name.  
   Figure 3. MCP tools list

## Result

After Build Agent authenticates the connection, you can chat with it to ask questions related to the MCP server.

*[\>]: and then