Skip to main content
Add an MCP connector from the official MCP Registry, npm, or a remote URL.

Usage

Arguments

Flags

Examples

Registry Lookup

When you pass a package name:
  • Full name (contains / or starts with @) — Direct lookup in registries
  • Short name — Searches registries and presents matching results for selection
If multiple results are found, Ultra shows an interactive selector (up to 9 results).

URL Mode

When you pass an HTTP(S) URL:
  • Ultra derives a connector name from the hostname (e.g., https://mcp.slack.comslack)
  • Tests the connection and detects authentication requirements
  • For OAuth connectors, authorization happens at runtime
  • For token-based auth, prompts for the token during setup

Connection Testing

For both registry and URL connectors, Ultra tests the connection:
  • Stdio connectors — Probes the connector with the MCP handshake. If the default args fail, automatically tries common fixes (e.g., appending --stdio)
  • HTTP connectors — Tests connectivity and detects auth requirements (OAuth, Bearer token, API key)

Configuration

Added connectors are written to Ultra’s config file. Environment variables and auth tokens are collected during the interactive flow or can be set later: