Skip to main content
The Plugin Library keeps the plugins you reach for again and again, such as premium plugins you buy as ZIPs or your own private plugins on GitHub. Once a plugin is in the library, you or your AI agent can install it on any ready sandbox by its name, without hunting for the file. The library belongs to your workspace. Members who can deploy plugins can install from it; changing it needs the same permission as Templates and Blueprints.

​
Add a plugin

Open Plugins in the SandyWP app and select Add plugin.
  • Upload ZIP. Choose the plugin ZIP (up to 50 MB). The name defaults to the file name. Uploading again under the same name replaces the stored ZIP, so updating a premium plugin is one upload.
  • GitHub release. Pick a repository that SandyWP’s GitHub App can read. Every install checks the repository’s latest published release and uses its .zip asset, so sandboxes always get the newest version.
For GitHub, attach the built plugin ZIP to each release. SandyWP uses the only .zip asset, or the one named <repository>.zip when a release has several. GitHub’s automatic “Source code” archives are never used: their folder name changes with every tag, which WordPress would treat as a new plugin.
To give the GitHub App access to a repository, open Account → GitHub. See GitHub.

​
Install a plugin

From the dashboard, select Install next to a plugin and choose a ready sandbox. The plugin is installed and activated. From an AI agent connected to the SandyWP MCP server, just ask, for example “install gravityforms on my-shop”. The agent calls sandywp_list_plugin_library to find the name and sandywp_deploy_plugin with libraryPlugin to install it. The agent never needs the ZIP file. From the CLI:
From the API, send { "libraryPlugin": "gravityforms" } to POST /api/app/sites/{id}/deploy-plugin.

​
License keys

The library stores plugin files, not license keys. Activate a premium plugin’s license inside the sandbox as you normally would. Only add plugins you are licensed to use in your workspace.