Skip to main content
The Connectors page in Ultra Hub provides visibility into all upstream MCP connectors used across your organization. See which connectors are active, how they’re performing, and who’s using them.

Connector List

The main view shows a card for each MCP connector with key metrics: Click any connector card to view detailed information.
The transport badge is derived from the most recent trace for each connector, so it reflects how the connector is actually being reached. Older traces recorded before this field was captured appear without a badge.

Blocking a connector

Admins see a Block action on each row. Clicking it opens a confirmation dialog and creates an organization-wide rule that denies every tool call to that connector, for every user. Blocked connectors can be reviewed, edited, or unblocked from the Governance page.

Connector Detail View

The detail view provides in-depth metrics and breakdowns for a single connector. The connector’s transport type (stdio, http, or sse) appears as a badge next to the connector name in the page header, making it easy to tell at a glance how Ultra is reaching the connector.

Stats Overview

At the top, summary cards show:
  • Total Requests — Lifetime request count
  • Success Rate — Overall success percentage
  • Errors — Total error count
  • Tools — Number of unique tools available
  • Avg Latency — Average response time

Tools Tab

A table of every tool called on this connector: Use this to identify your most-used tools, spot error-prone tools, and find performance bottlenecks.

Devices Tab

Shows which devices are routing traffic to this connector:

Users Tab

Shows which users are interacting with this connector:

Requests Tab

A full paginated trace history for this connector. Each entry links to the detailed trace view. Use Load More to page through older requests. In Hub mode, both this tab and the Overview preview show who made each request, linked to that user’s identity.

Use Cases

  • Performance monitoring — Identify slow connectors or tools that need optimization
  • Usage analysis — Understand which connectors and tools your team relies on most
  • Troubleshooting — Drill into error patterns by connector, tool, device, or user
  • Capacity planning — Track request volumes and device counts to plan infrastructure