Skip to main content
Because Ultra is itself an MCP server, it exposes built-in tools that your AI client can call directly. This means you can search for, add, migrate, and monitor MCP servers without leaving your conversation.
These tools are available automatically when Ultra is connected to your AI client. No extra configuration needed.
These are Ultra’s own built-in tools. For the inventory of tools your upstream servers (GitHub, Linear, and so on) expose — with usage, enforcement, and blocking — see Server Tools in Ultra Hub.

​
Available Tools

Ultra provides these built-in tools:
ultra_servers renders an interactive panel to view, discover, add, and reconnect servers visually. See the MCP App page.
In addition to these management tools, Ultra aggregates all tools from your upstream servers and exposes them through a single connection. Each upstream tool is namespaced with its server name (e.g., github:search_code, notion:search).

​
ultra_status

Check that Ultra is running and see what’s connected. Example prompts:
  • “Check my Ultra status”
  • “How many MCP tools do I have connected?”
Returns: Ultra version, number of upstream servers, and total aggregated tool count. Search the official MCP registry and npm for servers to add. Example prompts:
  • “Search for a Notion MCP server”
  • “Find MCP servers for databases”
  • “Search npm for filesystem MCP servers”
Parameters: Returns: Server names, descriptions, versions, authors, download counts, and required environment variables.

​
ultra_add

Add an MCP server and make its tools available immediately. No restart required. Example prompts:
  • “Add the GitHub MCP server”
  • “Install the filesystem server so you can read my project files”
  • “Add the Slack MCP server at https://mcp.slack.com/mcp”
Parameters: What happens:
  1. Ultra resolves the server from the registry or connects to the URL
  2. Validates any required environment variables
  3. Adds the server to your Ultra config
  4. Hot-loads the server immediately so new tools are available without restarting
Ultra hot-loads the server with no restart of its own, and most clients pick up the new tools automatically. Some clients (for example, Codex CLI) only refresh their tool list on reconnect — if the new tools don’t appear, refresh or restart that client or start a new conversation.

​
ultra_migrate

Discover MCP servers already configured in your AI clients and import them into Ultra. Example prompts:
  • “Migrate my existing MCP servers to Ultra”
  • “What MCP servers do I have that aren’t going through Ultra yet?”
Parameters: What happens:
  1. Ultra scans your AI clients (Claude Desktop, Cursor, Codex, etc.) for configured MCP servers
  2. Shows you what it found, including command and connection details
  3. On execute, imports selected servers into Ultra’s config and hot-reloads them
  4. Duplicate servers configured across multiple clients are merged automatically
After migration, restart your MCP client(s) so they route through Ultra instead of connecting directly.

​
ultra_reconnect

Re-authenticate a server whose sign-in has expired, in place. Used automatically by the Reconnect button in the MCP App. Example prompts:
  • “Reconnect the Notion server”
  • “Which servers need me to sign in again?”
Parameters: What happens: For OAuth servers, Ultra returns a sign-in link (and opens your browser when it can); once you finish, the server’s tools come back automatically. It applies to local gateways only, and only to servers that use browser sign-in — token or API-key servers are recovered with ultra config set-token <server> instead. From a terminal, ultra reconnect <server> is the CLI equivalent for a single OAuth server. It saves the new token but can’t refresh a running client, so restart your MCP client afterward.

​
Upstream Tool Aggregation

Beyond its built-in tools, Ultra aggregates every tool, resource, and prompt from all your connected upstream servers into a single MCP connection. Your AI client sees one server (Ultra) with all tools available. Tools are automatically namespaced by server name to avoid conflicts:
This means you can add a new upstream server and its tools appear alongside everything else. No client reconfiguration needed.

Upstream Servers

Add and configure MCP servers manually via CLI or config file

Migrate Servers

Import existing servers using the CLI wizard