Upstream Connectors

Ultra proxies requests to one or more upstream MCP connectors. Connectors can use stdio transport (local commands) or HTTP transport (remote URLs).

Only add MCP connectors from official or trusted sources. Untrusted community connectors can execute arbitrary code on your machine (stdio transport) or receive sensitive data from your AI agents (HTTP transport). Stick to connectors from the official MCP Registry, verified publishers, or connectors your organization has reviewed and approved.

Agent
Terminal

Add Connectors Through Your Agent

The simplest way to add MCP connectors is to ask your agent to do it for you. Since Ultra is already connected to your agent, just tell it what services you want to connect:

“Connect to the Notion connector”
“Add the GitHub connector”
“Set up the filesystem connector so you can read my project files”
“Add the Linear connector”

Your agent will work with Ultra to search the registry, install the connector, and configure any required authentication (API keys, OAuth, etc.).

In agents that support MCP Apps, you can view, discover, add, and reconnect connectors from an interactive panel — see the ultra_servers MCP App.

Ultra hot-loads the new connector with no restart of its own. Most agents pick up the new tools automatically; if they don’t appear, refresh or restart your agent.

Make sure your agent installs the official MCP connector for each service — not a random community fork. Look for connectors published by the service provider (e.g., @notionhq/notion-mcp-server) or from the official MCP Registry. If you’re unsure, ask your agent to confirm the publisher before installing.

You can also ask your agent to list your current connectors (“What connectors do I have connected?”) or remove ones you no longer need.

Popular Connectors

Select a connector to see setup instructions.

Notion

Ask your agent: “Add the Notion connector”Notion uses OAuth. You will be redirected to Notion in your browser to authorize access to your workspace. Tokens are stored and refreshed automatically.You need to be a member of the Notion workspace you want to connect.

Slack

Slack needs a Slack app in your workspace before Ultra can connect. Slack’s MCP server does not register clients automatically, so the OAuth flow needs a pre-registered app’s client ID and secret.

Create or open an app at api.slack.com/apps. Slack allows only internal or directory-published apps to use MCP.
Under OAuth & Permissions, grant the user token scopes in the table below, then install the app to your workspace.
Copy the Client ID and Client Secret from Basic Information > App Credentials.
Ask your agent: “Add the Slack connector”
Ask your agent to set the credentials, for example “Set the Slack connector’s client_id and client_secret” followed by the two values. Your agent applies them with the ultra_configure tool.
Ask your agent to reconnect Slack. Authorize in your browser when Slack prompts you.

Required scopes

Ultra currently requests every Slack MCP user-token scope below. Add the same scopes to the Slack app before reconnecting; otherwise Slack may reject the request or issue a token that cannot use every Slack MCP tool.

Capability	User token scopes
Search your workspace	`search:read.public`, `search:read.private`, `search:read.mpim`, `search:read.im`, `search:read.files`, `search:read.users`
Read conversation history	`channels:history`, `groups:history`, `im:history`, `mpim:history`
Send messages and react	`chat:write`, `channels:write`, `groups:write`, `im:write`, `mpim:write`, `reactions:write`
Look up channels and people	`channels:read`, `groups:read`, `mpim:read`, `users:read`, `users:read.email`
Read files and emoji	`files:read`, `emoji:read`
Work with canvases	`canvases:read`, `canvases:write`

Linear

Ask your agent: “Add the Linear connector”Linear uses OAuth. Authorize in your browser when prompted.

GitHub

Ask your agent: “Add the GitHub connector”You will be prompted for a Personal Access Token (PAT). Create one at github.com/settings/tokens with the scopes you need (typically repo and read:org).Use a fine-grained PAT scoped to only the repositories you need for better security.

Figma

Ask your agent: “Add the Figma connector”Figma uses OAuth. You will be redirected to Figma in your browser to authorize access to your files and projects.

AWS

Ask your agent: “Add the AWS connector”You will need AWS credentials configured on your machine (via ~/.aws/credentials or environment variables).

Jira

Ask your agent: “Add the Jira connector”You will be prompted for your Jira instance URL and an API token. Create one at id.atlassian.com/manage-profile/security/api-tokens.

Mintlify

Ask your agent: “Add the Mintlify connector”You will need your Mintlify project subdomain or API key.

Salesforce

Ask your agent: “Add the Salesforce connector”Salesforce uses OAuth. You will be redirected to Salesforce in your browser to authorize access to your org.

Datadog

Ask your agent: “Add the Datadog connector”You will be prompted for your Datadog API key and application key. Find these in your Datadog org settings under API Keys.

PostgreSQL

Ask your agent: “Add the PostgreSQL connector”You will be prompted for your database connection string. Use a read-only database user when possible.

Vanta

Ask your agent: “Add the Vanta connector”Vanta uses OAuth. You will be redirected to Vanta in your browser to authorize. Once approved, the token is stored and refreshed automatically.You need an active Vanta account with appropriate permissions. If you see an authentication error, check with your Vanta admin that your account has API access enabled.

Filesystem

Ask your agent: “Add the filesystem connector for my project files”The filesystem connector runs locally and does not require authentication. You will be asked which directories to allow access to.Only grant access to directories you are comfortable sharing with your AI agent. Never point it at your home directory or root.

Supported Agents

Ultra works with all major MCP-compatible AI agents:

Agent	Type
Claude Desktop	Desktop app
Cursor	IDE
VS Code	IDE
GitHub Copilot	IDE (via VS Code)
Claude Code	CLI
Codex	CLI
Windsurf	IDE
Roo Code	VS Code extension
Goose	CLI
Gemini	Desktop app
Antigravity	IDE / CLI
LM Studio	Desktop app
Amazon Q Developer	CLI
Zed	IDE
Ona	Cloud dev environment
Hermes	Agent framework

Run ultra doctor to see which agents are detected on your machine, or ultra install to configure a specific agent.

Adding Connectors from Registry

The easiest way to add connectors is from the MCP registry:

# Search for connectors
ultra search filesystem

# Add by name (searches registries)
ultra add filesystem

# Add by full package name
ultra add @modelcontextprotocol/server-filesystem

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

When adding from the registry, Ultra automatically tests the connection, detects authentication requirements, and prompts for any required configuration (API keys, file paths, etc.).

Adding Remote Connectors by URL

Add HTTP-based MCP connectors directly by URL:

# Add a remote connector
ultra add https://mcp.example.com/mcp

# With a custom name
ultra add https://remote.example.com/mcp --name myconnector

Ultra auto-detects transport type and authentication requirements. If the connector requires OAuth, you’ll be prompted to authorize when it’s first used. For token-based auth, Ultra prompts for the token during setup.Connectors that don’t register OAuth clients automatically, such as Slack, need a pre-registered app’s client_id and client_secret on the entry as well. See the connector’s own instructions below.

Popular Connectors

Select a connector below for specific setup instructions.

Notion

ultra add notion

Notion uses OAuth. Ultra opens your browser for authorization. Tokens are stored and refreshed automatically.You need to be a member of the Notion workspace you want to connect.

Slack

ultra add https://mcp.slack.com/mcp --name slack

Slack’s MCP server does not register clients automatically, so adding the URL is not enough on its own. Create or open an app at api.slack.com/apps, grant it the user token scopes listed below, then copy the Client ID and Client Secret from Basic Information > App Credentials.There is no CLI flag for these values. The quickest way to apply them is to ask your agent to set the Slack connector’s client_id and client_secret, which it does with the ultra_configure tool. To set them by hand instead, add them to the slack entry in your config file (ultra config path prints its location):

upstream:
  slack:
    url: https://mcp.slack.com/mcp
    client_id: 1234567890.9876543210
    client_secret: abc123def456
    enabled: true

Paste the raw values; quotes are not required. Either way, reconnect Slack afterward with ultra reconnect slack. Ultra opens your browser to authorize, and once approved your agent can send messages, search conversations, and interact with your workspace.

Required scopes

Capability	User token scopes
Search your workspace	`search:read.public`, `search:read.private`, `search:read.mpim`, `search:read.im`, `search:read.files`, `search:read.users`
Read conversation history	`channels:history`, `groups:history`, `im:history`, `mpim:history`
Send messages and react	`chat:write`, `channels:write`, `groups:write`, `im:write`, `mpim:write`, `reactions:write`
Look up channels and people	`channels:read`, `groups:read`, `mpim:read`, `users:read`, `users:read.email`
Read files and emoji	`files:read`, `emoji:read`
Work with canvases	`canvases:read`, `canvases:write`

Slack allows only internal or directory-published apps to use MCP.

Linear

ultra add linear

Linear uses OAuth. Authorize in your browser when prompted. Your agent can then read and manage issues, projects, and cycles.

GitHub

ultra add github

GitHub requires a Personal Access Token (PAT). Ultra prompts you to enter it during setup. Create one at github.com/settings/tokens with the scopes you need (typically repo and read:org).Use a fine-grained PAT scoped to only the repositories you need for better security.

Figma

ultra add https://mcp.figma.com/mcp --name figma

Figma uses OAuth. Ultra opens your browser for authorization. Tokens are stored and refreshed automatically.

AWS

ultra add aws

The AWS connector uses your local AWS credentials (~/.aws/credentials or environment variables). Make sure aws configure is set up before adding.

Jira

ultra add jira

Jira requires your instance URL and an API token. Create one at id.atlassian.com/manage-profile/security/api-tokens. Ultra prompts for both during setup.

Mintlify

ultra add mintlify

When prompted, enter your Mintlify project subdomain or API key.

Salesforce

ultra add salesforce

Salesforce uses OAuth. Ultra opens your browser for authorization. Tokens are stored and refreshed automatically.

Datadog

ultra add datadog

Datadog requires an API key and application key. Find these in your Datadog org settings under API Keys. Ultra prompts for both during setup.

PostgreSQL

ultra add postgres

When prompted, enter your PostgreSQL connection string (e.g., postgresql://user:pass@host:5432/dbname). Use a read-only database user when possible.

Vanta

ultra add https://mcp.vanta.com/mcp --name vanta

Vanta uses OAuth. Ultra detects this automatically and opens your browser to authorize. Once approved, tokens are stored and refreshed automatically.You need an active Vanta account with appropriate permissions. If you see an authentication error, check with your Vanta admin that your account has API access enabled.

Filesystem

ultra add filesystem

The filesystem connector runs locally (stdio transport) and does not require authentication. When prompted, specify the directory paths you want to allow access to.Only grant access to directories you are comfortable sharing with your AI agent. Never point it at your home directory or root.

Adding Connectors Manually

Use ultra connectors add for full control:

# Stdio transport (local command)
ultra connectors add filesystem \
  --command npx \
  --args "-y @modelcontextprotocol/server-filesystem /tmp"

# HTTP transport (remote URL)
ultra connectors add remote-api --url https://mcp.example.com/sse

# With environment variables
ultra connectors add github \
  --command npx \
  --args "-y @modelcontextprotocol/server-github" \
  --env "GITHUB_TOKEN=ghp_xxx"

# Add in disabled state
ultra connectors add test-connector --command ./test-server --disabled

Managing Connectors

# List all connectors
ultra connectors

# Enable/disable
ultra connectors enable filesystem
ultra connectors disable filesystem

# Remove
ultra connectors remove filesystem
ultra connectors remove filesystem --force  # Skip confirmation

Stdio vs HTTP Transport

Stdio Transport

For connectors that run as local processes. Ultra spawns the process and communicates over stdin/stdout.

upstream:
  filesystem:
    command: npx
    args: ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
    env:
      NODE_ENV: production
    enabled: true

HTTP Transport

For remote connectors. Ultra connects over HTTP/SSE.

upstream:
  notion:
    url: "https://mcp.notion.so"
    headers:
      Authorization: "Bearer secret_xxx"
    enabled: true

Authentication

Token-Based Auth

Set auth tokens for HTTP connectors:

# Set during add (interactive)
ultra add https://mcp.example.com/sse

# Set after adding
ultra config set-token my-connector YOUR_TOKEN

# Set a custom header
ultra config set-header my-connector X-API-Key YOUR_KEY

Tokens are stored as Authorization: Bearer {token} headers in the config file.

OAuth2

Ultra supports OAuth2 authentication for upstream connectors that require it. The OAuth flow is handled automatically at runtime — when a connector requires authorization, Ultra opens a browser for you to complete the flow and stores the tokens for future requests.

Environment Variables

For stdio connectors, pass secrets via environment variables instead of hardcoding them in args:

upstream:
  github:
    command: npx
    args: ["-y", "@modelcontextprotocol/server-github"]
    env:
      GITHUB_TOKEN: "ghp_xxxxxxxxxxxx"
    enabled: true

Getting Started

Ultra Hub

Observability

Concepts

Upstream Connectors

Add Connectors Through Your Agent

Popular Connectors

Required scopes

Supported Agents

Adding Connectors from Registry

Adding Remote Connectors by URL

Popular Connectors

Required scopes

Adding Connectors Manually

Managing Connectors

Stdio vs HTTP Transport

Stdio Transport

HTTP Transport

Authentication

Token-Based Auth

OAuth2

Environment Variables

​Add Connectors Through Your Agent

​Popular Connectors

​Required scopes

​Supported Agents

​Adding Connectors from Registry

​Adding Remote Connectors by URL

​Popular Connectors

​Required scopes

​Adding Connectors Manually

​Managing Connectors

​Stdio vs HTTP Transport

​Stdio Transport

​HTTP Transport

​Authentication

​Token-Based Auth

​OAuth2

​Environment Variables

Add Connectors Through Your Agent

Popular Connectors

Required scopes

Supported Agents

Adding Connectors from Registry

Adding Remote Connectors by URL

Popular Connectors

Required scopes

Adding Connectors Manually

Managing Connectors

Stdio vs HTTP Transport

Stdio Transport

HTTP Transport

Authentication

Token-Based Auth

OAuth2

Environment Variables