ultra_servers — that renders a connected-connector manager right inside AI agents that support MCP Apps. You can check connector health, discover and add new connectors, and reconnect connectors that need sign-in without leaving your conversation.
The
ultra_servers app renders in agents that support the open MCP Apps capability. In agents that don’t, ultra_servers returns the same information as a plain text list, and every action is still available through the ultra_status, ultra_search, ultra_add, and ultra_reconnect tools.Opening the app
Ask your AI agent to show your connectors, or call theultra_servers tool directly:
- “Show my Ultra connectors”
- “Open the Ultra connectors panel”
- “Which of my MCP connectors need attention?”
Connected tab
The Connected tab lists every connector Ultra is proxying, with a header summarizing how many are healthy (for example, “14 connectors · 12 healthy”). Each connector row shows:
A Refresh button re-fetches Ultra’s current status snapshot so the list reflects the latest state — for example, after you reconnect a connector. It updates what’s displayed; it does not re-probe or retry a failed or timed-out connector.
Connector rows never expose secrets. The app renders from a sanitized snapshot that omits URLs, headers, environment variables, and credentials.
Reconnecting a connector
When a connector’s authorization expires, its status changes to Needs auth and it stops exposing tools until you sign in again. How you recover depends on how the connector authenticates.OAuth connectors
Connectors that authenticate with OAuth show a Reconnect button. Clicking it opens your browser to sign in again; once you finish, Ultra restores the connection with no restart of its own. Most agents then show the connector’s tools again automatically; some only refresh their tool list on restart, so if the tools don’t reappear, refresh or restart your agent. Behind the button, the app calls theultra_reconnect tool. You can also trigger it directly in any agent — for example, “Reconnect the Monaco connector” — and Ultra returns a sign-in link to open in your browser.
From a terminal, ultra reconnect <connector> does the same re-auth for a single OAuth connector — useful when your agent can’t surface the reconnect link. Unlike the in-agent reconnect, the CLI can’t refresh a running agent, so restart your MCP agent afterward to load the new token.
ultra_reconnect runs on local devices only; reconnecting a connector on a hosted device is not yet supported.Token and API-key connectors
Connectors that authenticate with a token, API key, or environment credential can’t be fixed by a browser sign-in. If one starts failing because its credential is invalid or expired, update the credential from the terminal instead:Discover tab
The Discover tab searches the official MCP registry and npm, then lets you add a connector straight from the results. When a connector connects, it hot-loads with no restart — Ultra makes its tools available immediately. A connector that still needs OAuth sign-in or configuration, or that fails to hot-load, is saved and listed as non-healthy until you finish authenticating or fix its configuration. Discovery is backed by theultra_search and ultra_add tools, so you can do the same thing conversationally (“Search for a Postgres MCP connector and add it”) in any agent.
Ultra hot-loads new tools with no restart of its own. Most agents pick up the new tools automatically; some agents (for example, Codex CLI) only refresh their tool list on reconnect, so if new tools don’t appear, refresh or restart that agent or start a new conversation.
Related
Ultra MCP Tools
The built-in tools the app is built on: status, search, add, migrate, and reconnect
Upstream Connectors
Add, configure, and manage MCP connectors from the agent or the terminal
Configure Agents
Connect Ultra to the AI agents that render the app
Migrate Connectors
Import MCP connectors you already have configured