ultra add

​

Usage

ultra add <server|url> [flags]

​

Arguments

​

Flags

​

Examples

# Add the official filesystem server
ultra add @modelcontextprotocol/server-filesystem

# Add by short name (searches registries)
ultra add filesystem

# Add with a custom name
ultra add @modelcontextprotocol/server-filesystem --name myfiles

# Add without prompts (use defaults)
ultra add filesystem --yes

# Add a remote server by URL
ultra add https://mcp.slack.com/mcp

# Add a remote server with a custom name
ultra add https://remote.example.com/mcp --name myserver

​

Registry Lookup

• Full name (contains / or starts with @) — Direct lookup in registries
• Short name — Searches registries and presents matching results for selection

​

URL Mode

• Ultra derives a server name from the hostname (e.g., https://mcp.slack.com → slack)
• Tests the connection and detects authentication requirements
• For OAuth servers, authorization happens at runtime
• For token-based auth, prompts for the token during setup

​

Connection Testing

• Stdio servers — Probes the server with the MCP handshake. If the default args fail, automatically tries common fixes (e.g., appending --stdio)
• HTTP servers — Tests connectivity and detects auth requirements (OAuth, Bearer token, API key)

​

Configuration

ultra config set-token my-server YOUR_TOKEN