ultra search only lists connectors. It does not install one.
Usage
-- before any command argument that starts with a dash, so Ultra does not read it as its own flag.
Arguments
Flags
Ultra rejects environment variables that can change how a process starts, such as
PATH and HOME.
Examples
Local connectors
The default transport isstdio. The second argument is the program to run, and anything after it is that program’s arguments.
A URL is not a stdio target. Pass --transport http or --transport sse when the second argument is a URL.
Remote connectors
--transport http selects Streamable HTTP. --transport sse selects SSE. Remote transports do not take command arguments.
The URL must be http or https, include a host, and must not contain a username, password, or fragment. Put credentials in --header instead. An http:// URL whose host is not loopback prints a warning: traffic and credentials are not encrypted.
An enabled remote connector is saved before Ultra checks whether browser sign-in is required. The check is skipped when:
- the connector was added with
--disabled - an
Authorizationheader was set with--header - the URL contains query parameters
ultra reconnect <name> to try again. A connector that does not ask for browser sign-in is left as configured.
--client-secret reads MCP_CLIENT_SECRET when it is set. Otherwise it prompts on a terminal and does not put the secret in shell history. A non-interactive shell with no MCP_CLIENT_SECRET fails.
After adding
The entry is written to the config file immediately. Restart your agent to use the new connector. If your organization blocks that connector,ultra add stops before it writes the config.
ultra connectors add writes an entry from --command or --url and does not start sign-in. Use it when you want that flag form, including a description. Use ultra config set-token to attach a bearer token after the connector exists.