This article explains how to upload a custom plugin or import one from GitHub when the plugin you need is not in the catalog, what the package must contain, and how personal and organization plugins differ. A custom plugin bundles skills and connectors into one package that Perplexity Computer can install in a single step.
For adding a single custom skill or custom connector, see How to use Computer Skills and Adding Custom Remote Connectors. To add either one to your own account, start from the Add custom menu.
Plugin upload needs the Plugins page. If your organization hasn’t turned on Plugins yet, keep using Customize → Connectors and Skills to add skills and connectors. Everything there works as before.
Before you start
For plugins that include skills, a plan that includes Perplexity Computer.
A
.zipfile with aplugin.jsonmanifest (see What a plugin package contains), or the URL of a public GitHub repository.If you belong to an organization, permission from your administrator to upload or create personal or organization plugins and skills.
What a plugin package contains
A plugin package is a .zip file with a plugin.json manifest. The manifest must include a name. A description is optional and can be omitted or empty. If provided, it must be a string of up to 1,024 UTF-8 bytes. Put plugin.json at the root of the archive, or upload a Claude Code or Codex plugin as it is. When there is no plugin.json at the root, Perplexity reads .claude-plugin/plugin.json or .codex-plugin/plugin.json instead. If you compress the plugin folder itself, that single top-level folder is fine. The package can contain:
Skills: folders that each contain a
SKILL.mdfile with a YAML frontmatter block (name and description) and any supporting files the skill uses.Connectors: remote MCP servers listed in an
mcp.jsonfile at the root of the package (or.mcp.json, the Claude Code and Codex name), not inplugin.json. Each server needs an HTTPS address and atypeofstreamable-http,http, orsse. Each server is added as a connector, or matched to a connector your organization already has, that members connect with their own account. A server your account is not allowed to add as a connector is skipped.
A plugin must include at least one skill or connector. Limits per plugin:
Up to 32 skills
Up to 1,000 files
Up to 20 MB uncompressed
Up to 15 MCP servers
If the package lists more than 15 servers, Perplexity imports only the first 15. Perplexity skips servers beyond the limit, local stdio servers, servers without a type, servers that require fixed headers, server URLs that contain unresolved variable placeholders, and servers your account is not allowed to add as a connector. The upload still succeeds. After uploading, open the plugin’s page and confirm every connector you expected is listed.
Upload a plugin
Open the Plugins page
Select Plugins in the sidebar.
Select Add custom, then Upload plugin or skill
If you are allowed to create plugins for your organization, you also see Upload plugin or skill to organization.
Drag your .zip file into the upload area, or click to choose it
The upload area shows the file requirements.
Check that the plugin's skills and connectors are listed
The plugin opens on its own page. If you uploaded a personal plugin, it is installed for you right away.
Connect any connectors you want to use
If the upload is rejected, check that the manifest includes a name and that it’s at the root of the archive or in the Claude Code or Codex location.
Import a plugin from GitHub
You can import a plugin directly from a public GitHub repository instead of downloading and zipping it yourself. The same file requirements and limits apply as for an uploaded .zip.
Open the Plugins page
Select Plugins in the sidebar.
Select Add custom, then Import plugin from GitHub
Paste the repository URL
Only public repositories can be imported. To import a single plugin from a repository that contains several, paste the URL of that plugin’s folder.
Check that the plugin's skills and connectors are listed
How to verify it worked
The plugin opens on its own page with its skills and connectors listed, and appears on the Installed tab. If a connector you expected is missing, check the import rules above.
Personal and organization plugins
Personal plugins are for your own use.
Organization plugins appear on the Organization tab of the Plugins page for everyone in your organization. They are not installed for anyone automatically. An administrator can install an organization plugin for every member. If you created an organization plugin, you can request installation for everyone from its page. The request goes to your administrators, or, if your organization lets members install plugins they created, the plugin is installed for everyone right away.
If you belong to an organization, your administrator controls whether you can upload or create personal plugins and skills, and whether you can create organization plugins and skills. If you have a personal plugin you want to share, open it and select Transfer to organization; your personal preferences for the plugin are preserved. Administrators manage organization plugins from Organization settings → Plugins and skills; see Manage plugins for your organization.
Members cannot create organization connectors, including by uploading a plugin that declares a new connector. A plugin you upload can reference connectors your organization already has. Connectors inside your plugin follow your organization’s connector settings and role permissions.
Update or delete a plugin you uploaded
To update a plugin, open it, select More actions, then Replace file to upload a new .zip. To remove it entirely, choose Delete plugin. Deleting permanently removes the plugin and its bundle; it does not disconnect the connectors it referenced. To stop using a plugin without deleting it, select Uninstall instead. See Find, install, and remove plugins.
Related articles
Need more help?
Contact us via Help > Contact Support. Include the task link if your question is about a specific Computer task.