> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ultra.security/llms.txt
> Use this file to discover all available pages before exploring further.

# Ultra MCP Tools

> Manage MCP servers directly from your AI client using Ultra's built-in tools

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.

<Note>
  These tools are available automatically when Ultra is connected to your AI client. No extra configuration needed.
</Note>

<Info>
  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](/hub/tools) in Ultra Hub.
</Info>

## Available Tools

Ultra provides these built-in tools:

| Tool              | What it does                                                                                                                  |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| `ultra_status`    | Check Ultra's version, connected servers, and total tool count                                                                |
| `ultra_search`    | Search the official MCP registry and npm for servers                                                                          |
| `ultra_add`       | Install a server from a registry or URL, hot-loaded immediately                                                               |
| `ultra_migrate`   | Discover and import MCP servers already configured in your clients                                                            |
| `ultra_reconnect` | Re-authenticate a server that needs sign-in, without restarting Ultra (some clients may need a refresh)                       |
| `ultra_servers`   | List connected servers with live status, and open the interactive [MCP App](/getting-started/mcp-app) to manage them visually |

<Tip>
  `ultra_servers` renders an interactive panel to view, discover, add, and reconnect servers visually. See the [MCP App](/getting-started/mcp-app) page.
</Tip>

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.

## ultra\_search

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:**

| Parameter | Required | Description                                            |
| --------- | -------- | ------------------------------------------------------ |
| `query`   | Yes      | Search term (e.g., "filesystem", "github", "database") |
| `limit`   | No       | Max results to return (default: 10)                    |
| `source`  | No       | Filter by `official` or `npm`                          |

**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](https://mcp.slack.com/mcp)"*

**Parameters:**

| Parameter  | Required | Description                                                           |
| ---------- | -------- | --------------------------------------------------------------------- |
| `server`   | Yes      | Package name (e.g., `@modelcontextprotocol/server-filesystem`) or URL |
| `name`     | No       | Custom name for the server                                            |
| `env`      | No       | Environment variables (e.g., `{"GITHUB_TOKEN": "ghp_..."}`)           |
| `disabled` | No       | Add in disabled state (default: false)                                |

**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

<Note>
  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.
</Note>

## 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:**

| Parameter | Required | Description                                                     |
| --------- | -------- | --------------------------------------------------------------- |
| `action`  | Yes      | `discover` to list available servers, `execute` to migrate them |
| `servers` | No       | Specific server names to migrate (execute only)                 |

**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

<Warning>
  After migration, **restart your MCP client(s)** so they route through Ultra instead of connecting directly.
</Warning>

## ultra\_reconnect

Re-authenticate a server whose sign-in has expired, in place. Used automatically by the **Reconnect** button in the [MCP App](/getting-started/mcp-app).

**Example prompts:**

* *"Reconnect the Notion server"*
* *"Which servers need me to sign in again?"*

**Parameters:**

| Parameter | Required | Description             |
| --------- | -------- | ----------------------- |
| `name`    | Yes      | The server to reconnect |

**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>`](/cli/reconnect) 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:

```
github:search_code
github:create_pull_request
notion:search
notion:create_page
filesystem:read_file
filesystem:write_file
```

This means you can add a new upstream server and its tools appear alongside everything else. No client reconfiguration needed.

<CardGroup cols={2}>
  <Card title="Upstream Servers" icon="server" href="/configuration/upstream-servers">
    Add and configure MCP servers manually via CLI or config file
  </Card>

  <Card title="Migrate Servers" icon="arrow-right-arrow-left" href="/installation/migrate-servers">
    Import existing servers using the CLI wizard
  </Card>
</CardGroup>