---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Available Enterprise MCP Registries

# Available Enterprise MCP Registries {#ariaid-title1}

Release version: Australia  
Updated June 4, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Available Enterprise MCP Registries

The Enterprise MCP Registry provides pre-configured connection details to a variety of high-value MCP (Machine Communication Protocol) servers.
These servers offer integration points with popular enterprise collaboration, project management, design, and document management platforms, enabling ServiceNow customers to leverage natural-language interaction and automation capabilities across these services.
Show full answer Show less  

## Key MCP Servers and Their Capabilities

* **Zoom MCP Servers:**
  * **Zoom Meetings \& Collaboration:** Access meeting assets like AI summaries, recordings, transcripts, and documents through OAuth 2.0 authentication.
  * **Zoom Revenue Accelerator:** Provides sales-focused insights including conversation intelligence and CRM data, requiring a specific license.
  * **Zoom Whiteboard:** Enables creation and management of whiteboards and diagrams with OAuth 2.0 support.
  * **Zoom Docs:** Supports creation and retrieval of Zoom Docs and notes in Markdown format.
  * **Zoom Chat:** Facilitates team chat channel interactions, message handling, and contact management with write/update capabilities.
* **Atlassian Rovo:** Offers extensive integration with Jira, Confluence, and Compass, supporting over 46 tools and using OAuth 2.1 or API tokens for secure access. Legacy SSE endpoints are deprecated after June 30, 2026.
* **DocuSign:** Enables natural-language interactions with e-Signature and agreement management APIs, requiring OAuth 2.0 tokens.
* **Miro:** Supports whiteboard content management, diagram generation, and comment handling using OAuth 2.1 with dynamic client registration.
* **Figma:** Provides access to design files, components, and live UI capture through OAuth 2.0, enabling design context extraction and content creation.
* **Linear:** Covers project management workflows including issues, projects, and teams with OAuth 2.1 authentication.
* **Prisma:** Dual-mode architecture supporting database provisioning, schema migrations, and query execution with OAuth via Prisma Console.
* **Box:** File management, content search, sharing, and collaboration features supported through OAuth 2.1. Requires appropriate folder/file permissions for access.

## Authentication and Usage Notes

Most MCP servers use OAuth 2.0 or OAuth 2.1 for secure authentication, with some supporting server-to-server or headless operation modes. Certain services, like Zoom Revenue Accelerator and Atlassian Rovo, require specific licenses or administrative enablement for API tokens. All actions through these MCP servers respect existing user permissions within the connected platforms.

## Additional Configuration

Some connectors necessitate extra setup steps before client registration. ServiceNow customers should verify connector-specific requirements to ensure seamless integration and operation.  
Pre-configured connection information for a set of high‑value MCP Servers are available as part of the Enterprise MCP Registry.
The available MCP Servers are:  
{#mcp-reg-enterprise__table_xvp_l4d_mjc__entry__5}

| Server | URL/Endpoint | Services | Authentication | Notes |
|-|-|-|-|-|
| Zoom | `https://mcp.zoom.us/mcp/zoom/streamable` | * Meetings * Team Chat * Zoom Docs (search and retrieval) * AI summaries * Recordings and transcripts {#mcp-reg-enterprise__ul_yvp_l4d_mjc} | * OAuth 2.0 registered via Zoom App Marketplace. * Server-to-Server OAuth supported for headless use. {#mcp-reg-enterprise__ul_k1f_p4d_mjc} | Enables natural-language retrieval of meeting assets including AI summaries, docs, recordings, and whiteboards. |
| Zoom Revenue Accelerator | `https://mcp.zoom.us/mcp/revenue_accelerator/streamable` | * Conversation intelligence * Deal insights * Sales activity * CRM data * Coaching signals {#mcp-reg-enterprise__ul_zvp_l4d_mjc} | OAuth 2.0 registered via Zoom App Marketplace. | * Focused MCP surface for sales insights and deal intelligence. * Supports reviewing customer interactions and preparing follow-up notes. * Requires a Zoom Revenue Accelerator license. {#mcp-reg-enterprise__ul_jq4_v4d_mjc} |
| Zoom Whiteboard | `https://mcp.zoom.us/mcp/whiteboard/streamable` | * Whiteboard creation and management * Diagram generation {#mcp-reg-enterprise__ul_awp_l4d_mjc} | OAuth 2.0 registered via Zoom App Marketplace. | * Provides MCP tools for creating editable whiteboards and diagrams from prompts and locating existing boards. * Intended for workshop planning, visual collaboration, and diagram-generation use cases. * Exposes only boards the authenticated user can access. {#mcp-reg-enterprise__ul_g53_bpd_mjc} |
| Zoom Docs | `https://mcp.zoom.us/mcp/docs/streamable` | * Document creation * Document retrieval * Notes in Markdown {#mcp-reg-enterprise__ul_bwp_l4d_mjc} | OAuth 2.0 registered via Zoom App Marketplace. | * Supports creating new Zoom Docs from Markdown content and retrieving existing Zoom Docs or notes. * Designed for structured document generation and read-back flows. * Does not expose update or delete operations. {#mcp-reg-enterprise__ul_i2j_jpd_mjc} |
| Zoom Chat | `https://mcp.zoom.us/mcp/team_chat/streamable` | * Team chat channels * Messages * Contacts * Collaboration context {#mcp-reg-enterprise__ul_cwp_l4d_mjc} | OAuth 2.0 registered via Zoom App Marketplace. | * Focused MCP surface for chat channels, messages, contacts, and collaboration context. * Supports locating chat history, preparing summaries, and generating follow-ups. * Separate from the Zoom Workspace server; exposes write and update tools for messages and channels. {#mcp-reg-enterprise__ul_pwg_mpd_mjc} |
| Atlassian Rovo | `https://mcp.atlassian.com/v1/mcp` Legacy SSE endpoint (`/v1/sse`) deprecated after June 30, 2026. | * Jira * Confluence * Compass {#mcp-reg-enterprise__ul_dwp_l4d_mjc} | * OAuth 2.1. * API token supported for headless or machine-to-machine use if enabled by org admin. {#mcp-reg-enterprise__ul_ndq_qpd_mjc} | * Cloud-based bridge between an Atlassian Cloud site and compatible external tools. * All actions respect existing user permissions. Exposes 46+ tools across product areas. {#mcp-reg-enterprise__ul_pfb_5pd_mjc} |
| DocuSign | `https://mcp.docusign.com/mcp` | * e-Signature * Envelope management * Agreement workflows * Maestro * Navigator {#mcp-reg-enterprise__ul_ewp_l4d_mjc} | OAuth 2.0 access token is required per interaction. | * Enables natural-language interaction with DocuSign APIs, including authentication, API testing, and envelope creation. * Production connectors support seven API groups; additional endpoints accessible in developer mode. {#mcp-reg-enterprise__ul_t4l_2rd_mjc} |
| Miro | `https://mcp.miro.com/` | * Whiteboard and board content * Sticky notes, shapes, frames * Diagram generation * Comments {#mcp-reg-enterprise__ul_fwp_l4d_mjc} | OAuth 2.1 with dynamic client registration | * Supports content summarization, board creation, diagram generation, and comment resolution. * Users must supply a board URL in prompts; agents cannot discover or access boards not explicitly referenced. {#mcp-reg-enterprise__ul_xlr_frd_mjc} |
| Figma | * Remote: `https://mcp.figma.com/mcp` * Desktop/local: `http://127.0.0.1:3845/sse` {#mcp-reg-enterprise__ul_gwp_l4d_mjc} | * Design files and nodes * Components and variables * Styles * Code Connect * FigJam * Code-to-canvas capture {#mcp-reg-enterprise__ul_hwp_l4d_mjc} | OAuth 2.0 (browser-based; `mcp:connect` scope required; access limited to clients in the Figma MCP Catalog) | Enables design context extraction, native Figma content creation, and live UI capture as design layers. |
| Linear | * Streamable HTTP (recommended): `https://mcp.linear.app/mcp` * SSE (deprecated): `https://mcp.linear.app/sse` {#mcp-reg-enterprise__ul_iwp_l4d_mjc} | * Issues * Projects * Cycles * Comments * Teams and labels {#mcp-reg-enterprise__ul_jwp_l4d_mjc} | OAuth 2.1 with dynamic client registration (no API key required; browser OAuth flow) | Provides 25+ tools covering the full project management workflow. |
| Prisma | * Remote: `https://mcp.prisma.io/mcp` * Local: `npx prisma mcp` (CLI) {#mcp-reg-enterprise__ul_kwp_l4d_mjc} | * Prisma Postgres database provisioning * Schema migrations * Backups * Connection strings * SQL query execution * Database recovery {#mcp-reg-enterprise__ul_lwp_l4d_mjc} | OAuth (browser-based authentication via Prisma Console on first use) | Dual-mode architecture: local server handles development workflows (migrations, schema, queries); remote server manages Prisma Postgres infrastructure. |
| Box | `https://mcp.box.com` | * File management and operations * Folder operations and navigation * Content search and retrieval * Metadata extraction * Sharing and permissions * Collaboration context * Comments and workflows {#mcp-reg-enterprise__ul_ll1_lwy_ckc} | OAuth 2.1 | Cloud-based bridge for Box file content access. All actions respect existing user permissions. Supports natural-language file discovery, content summarization, and document retrieval. Users must have appropriate Box folder/file permissions. |
[Table 1. Enterprise MCP servers]

{#mcp-reg-enterprise__table_xvp_l4d_mjc}  
Note:  
Some connectors may require additional configurations. See [Additional connector configurations](https://www.servicenow.com/docs/attXxzscSQ1OMhC7C89APA "Some connectors may require additional configurations while registering client manually. These connectors and their required configurations are listed here.") for the list of supported connectors that require additional configurations. If your connector is listed, perform the required configurations before registering the client manually.

