Connect your AI to Ultrapack

Your access key

The key links your assistant to your account. It can only look things up: it never downloads, installs or changes anything in your account or on your sites. One key per account; creating a new one turns off the old one.

This key is for your AI only and has nothing to do with your Auto Updater token: creating or revoking it here won't affect your sites.

Sign in to create your key. It is free and works with all your assistants.

Sign in to create my key

Try asking

Which plugins on my sites are out of date? Start with the security ones.
Find a WooCommerce booking plugin and compare the top three.
What changed in the latest Elementor Pro release? Is it worth updating now?
How many downloads do I have left today, and when does my plan expire?

What your assistant can do

Everything is read-only. Downloads and updates still happen on the website and in the Auto Updater.

Any account

Search the catalog

Finds plugins, themes, kits and scripts by name or by what you need, with version and date.

Any account

Read an item's history

Current version, what changed in recent releases and the file's security scan result.

Any account

Check your plan

Plan, end date, today's downloads, site slots and single purchases with their update window.

With Auto Updater

Look at your sites

The sites connected to the Auto Updater and, on each one, what has a new version waiting, flagged when it is a security fix.

Active plan

Request an item

If it is not in the catalog, your assistant files a request with our team and gives you the ticket number.

Setup

1

Create your key

In the "Your access key" box above. It is shown only once. Create my key
2
Store the key in an environment variable

That keeps it out of project files. Then close and reopen your terminal or editor.
macOS / Linux
```
echo 'export ULTRAPACK_MCP_KEY="YOUR_KEY"' >> ~/.zshrc
```
Windows
```
setx ULTRAPACK_MCP_KEY "YOUR_KEY"
```

3

Add the server to your assistant

Pick yours and paste the config. After saving, restart the assistant and check that Ultrapack shows up in its tools list.

Claude Code

Where: in your terminal (once, for every project)

claude mcp add --transport http --scope user ultrapack https://www.ultrapackv2.com/mcp --header "Authorization: Bearer $ULTRAPACK_MCP_KEY"

In PowerShell, use $env:ULTRAPACK_MCP_KEY instead of $ULTRAPACK_MCP_KEY.

Cursor

Where: ~/.cursor/mcp.json

{
  "mcpServers": {
    "ultrapack": {
      "url": "https://www.ultrapackv2.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ULTRAPACK_MCP_KEY}"
      }
    }
  }
}

VS Code

Where: .vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "ultrapack-key",
      "description": "Ultrapack MCP key",
      "password": true
    }
  ],
  "servers": {
    "ultrapack": {
      "type": "http",
      "url": "https://www.ultrapackv2.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:ultrapack-key}"
      }
    }
  }
}

VS Code asks for the key the first time and stores it securely. Use Copilot in agent mode.

Codex CLI

Where: ~/.codex/config.toml

[mcp_servers.ultrapack]
url = "https://www.ultrapackv2.com/mcp"
bearer_token_env_var = "ULTRAPACK_MCP_KEY"

Gemini CLI

Where: ~/.gemini/settings.json

{
  "mcpServers": {
    "ultrapack": {
      "httpUrl": "https://www.ultrapackv2.com/mcp",
      "headers": {
        "Authorization": "Bearer $ULTRAPACK_MCP_KEY"
      }
    }
  }
}

Windsurf

Where: ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "ultrapack": {
      "serverUrl": "https://www.ultrapackv2.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ULTRAPACK_MCP_KEY}"
      }
    }
  }
}

Cline

Where: cline_mcp_settings.json

{
  "mcpServers": {
    "ultrapack": {
      "type": "streamableHttp",
      "url": "https://www.ultrapackv2.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      },
      "disabled": false
    }
  }
}

This client doesn't read environment variables, so the key is written in the file. Don't share or commit that file.

Zed

Where: settings.json

{
  "context_servers": {
    "ultrapack": {
      "url": "https://www.ultrapackv2.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

This client doesn't read environment variables, so the key is written in the file. Don't share or commit that file.

Claude Desktop

Where: claude_desktop_config.json

{
  "mcpServers": {
    "ultrapack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.ultrapackv2.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${AUTH}"
      ],
      "env": {
        "AUTH": "Bearer YOUR_KEY"
      }
    }
  }
}

Requires Node.js. Quit and reopen Claude Desktop after saving. This client doesn't read environment variables, so the key is written in the file. Don't share or commit that file.

Other

Any MCP client with remote HTTP (Streamable HTTP) works: send POST requests to the URL below with an Authorization: Bearer header and your key. For clients that only run local commands, use mcp-remote as shown for Claude Desktop.

POST https://www.ultrapackv2.com/mcp
Authorization: Bearer <ULTRAPACK_MCP_KEY>

Reference

Tools

Tool	What it does	Who can use it
`search_items`	Searches the whole catalog, up to 10 items per page and 50 per search.	Any account
`get_item`	One item in detail: version, date, changelog, security scan and whether your plan includes it.	Any account
`my_plan`	Plan, end date, today's downloads, site slots and single purchases.	Any account
`my_sites`	Sites connected to the Auto Updater, with status, last check-in and recent errors.	With Auto Updater
`site_updates`	What has a new version waiting on each site, with security fixes flagged.	With Auto Updater
`request_item`	Requests an item missing from the catalog (5 per day).	Active plan

Limits

60 requests every 10 minutes and 600 per day, per account.
Up to 50 results per search; use more specific words to find more.
Pending updates for each site refresh with every Auto Updater check-in, at most every 6 hours.

What the server never does

It never hands out download links or files.
It never installs, updates or reaches into your sites.
It never changes your account, plan or billing.

Troubleshooting

What you see	What to do
401 error or "invalid API key"	The key is wrong, was replaced, or the environment variable isn't loaded. Restart your terminal or create a new key.
403 error "not open for this account"	Access is still rolling out. Contact support to join.
429 error "rate limit"	You hit the request limit. Wait a few minutes; the error says how many seconds are left.
Your assistant opens a sign-in page in the browser	It didn't get the key. Check the Authorization header in the config.
Site updates come back empty	The site hasn't checked in with the Auto Updater yet. Wait up to 6 hours or run a check from the site's dashboard.
Windows: mcp-remote breaks the header	Write the header with no space after the colon (Authorization:${AUTH}) and keep the key in the AUTH variable, as in the Claude Desktop example.

Security

Treat the key like a password: don't paste it in chats, screenshots or repositories.
Think it leaked? Create a new one here: the old one stops working immediately.
Descriptions and changelogs are written by the vendors. The server tells your assistant to treat them as information, never as instructions.
Every call is logged for 30 days, with time and IP address, for your protection.

FAQ

Does it cost anything?

No. It is included with your account; what your assistant can see depends on your plan.

Can my assistant install anything on my site?

No. It only looks things up. Installs and updates still go through the website and the Auto Updater, with you in control.

Does it work in ChatGPT or claude.ai?

Not yet: they require direct sign-in with your account, which we are working on. Today it works with the assistants in the setup guide.

Can I use it on more than one computer?

Yes. The same key works in all your assistants; the request limit is counted per account.

Can my assistant see my customers' data?

No. It only sees the catalog, your plan and the list of sites connected to the Auto Updater, with the versions of our items.

The Ultrapack catalog, right inside your AI assistant

Your access key

Try asking

What your assistant can do

Search the catalog

Read an item's history

Check your plan

Look at your sites

Request an item

Setup

Create your key

Store the key in an environment variable

Add the server to your assistant

Claude Code

Cursor

VS Code

Codex CLI

Gemini CLI

Windsurf

Cline

Zed

Claude Desktop

Other

Reference

Tools

Limits

What the server never does

Troubleshooting

Security

FAQ