Plugins extend the Paperclip control plane with additional capabilities — custom integrations, workflow hooks, and third-party connectors are all delivered as npm packages installed into the Paperclip instance. The six plugin tools cover the full lifecycle: discover what’s available, install from the npm registry or a local path, inspect a specific plugin’s configuration and health, browse example implementations, and toggle plugins on or off without uninstalling them.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/bruhsb/paperclip-mcp/llms.txt
Use this file to discover all available pages before exploring further.
List Plugins
Audit installed plugins with optional status filter
Get Plugin
Inspect a specific plugin’s config and health
Install Plugin
Install a plugin from npm or a local path
List Examples
Browse reference plugin implementations
Enable Plugin
Re-activate a previously disabled plugin
Disable Plugin
Temporarily deactivate a plugin without uninstalling
paperclip_list_plugins
List installed plugins for the Paperclip instance. Supports filtering by lifecycle status and paginating through large plugin lists.Filter by plugin lifecycle status. Omit to return all plugins regardless of status.
Maximum plugins per page. Range 1–100. Defaults to
50.Number of plugins to skip for pagination. Defaults to
0.Output format.
markdown (default) produces a human-readable list; json returns a structured envelope.{ items: Plugin[], total, count, offset, limit, has_more, next_offset }. Each Plugin item contains: pluginKey, packageName, displayName, description, status, version.
Usage notes:
- Use when auditing which plugins are installed or finding plugins in an
errorstate that need attention. - For full plugin details including
healthandconfig, usepaperclip_get_pluginwith a specificpluginKey. - Filter by
status: "error"to quickly surface plugins that need remediation.
| Code | Meaning | Resolution |
|---|---|---|
| 401 | Authentication failed | Check PAPERCLIP_API_KEY |
| 403 | Permission denied | This tool requires a board (human-user) API key |
paperclip_get_plugin
Get detailed information about a specific installed plugin by its key, including configuration and health status.Plugin key (e.g.
paperclip.hello-world-example or @acme/plugin-linear). The key is URL-encoded automatically before the API request.Output format.
markdown (default) or json for structured output.pluginKey, packageName, displayName, description, status, version, config, health.
Usage notes:
- Use to inspect a plugin’s
configandhealthbefore enabling or modifying it. - To list all plugins at once, use
paperclip_list_pluginsinstead.
| Code | Meaning | Resolution |
|---|---|---|
| 401 | Authentication failed | Check PAPERCLIP_API_KEY |
| 403 | Permission denied | Requires board API key |
| 404 | Plugin not found | Verify the key with paperclip_list_plugins |
paperclip_install_plugin
Install a plugin from the npm registry or a local filesystem path into the Paperclip instance. This is an open-world operation — the API fetches the package from npm whenisLocalPath is false.
npm package name to install (e.g.
@paperclipai/plugin-hello-world-example). When isLocalPath is true, this is instead a local filesystem path.Specific package version to install (e.g.
1.2.3). Omit to install the latest published version.Set to
true when packageName is a local filesystem path rather than an npm package name. Useful for testing locally built plugins.pluginKey, packageName, status, message confirming the install outcome.
Usage notes:
- Use when adding a new plugin capability from the npm registry or a local build.
- If the plugin is already installed but disabled, use
paperclip_enable_pluginto re-activate it instead of reinstalling. - For discovering available example plugins to install, use
paperclip_list_plugin_examplesfirst.
| Code | Meaning | Resolution |
|---|---|---|
| 400 | Install failed (npm error) | Verify the package name exists in the npm registry |
| 401 | Authentication failed | Check PAPERCLIP_API_KEY |
| 403 | Permission denied | Requires board API key |
paperclip_list_plugin_examples
List available reference plugin implementations that can be installed to understand the plugin API surface.Output format.
markdown (default) or json for structured output.packageName, pluginKey, displayName, description, localPath, tag.
Usage notes:
- Use when exploring the plugin API surface or looking for a reference implementation to base new work on.
- To see the list of already-installed plugins, use
paperclip_list_pluginsinstead.
| Code | Meaning | Resolution |
|---|---|---|
| 401 | Authentication failed | Check PAPERCLIP_API_KEY |
| 403 | Permission denied | Requires board API key |
paperclip_enable_plugin
Enable a previously disabled plugin by its key. Safe to call even if the plugin is already enabled — the operation is idempotent.Plugin key (e.g.
paperclip.hello-world-example or @acme/plugin-linear). URL-encoded automatically.status confirming the plugin is now enabled.
Usage notes:
- Use when re-activating a plugin that was disabled without uninstalling it.
- If the plugin is not yet installed, use
paperclip_install_pluginfirst. - This call is idempotent — calling it on an already-enabled plugin is safe.
| Code | Meaning | Resolution |
|---|---|---|
| 401 | Authentication failed | Check PAPERCLIP_API_KEY |
| 403 | Permission denied | Requires board API key |
| 404 | Plugin not found | Verify the key with paperclip_list_plugins |
paperclip_disable_plugin
Disable an active plugin by its key without uninstalling it. The plugin’s configuration is preserved and it can be re-enabled later withpaperclip_enable_plugin.
Plugin key (e.g.
paperclip.hello-world-example or @acme/plugin-linear). URL-encoded automatically.status confirming the plugin is now disabled.
Usage notes:
- Use to temporarily deactivate a plugin without losing its installation or configuration.
- To permanently remove a plugin, use the uninstall flow — disabling is always reversible.
| Code | Meaning | Resolution |
|---|---|---|
| 401 | Authentication failed | Check PAPERCLIP_API_KEY |
| 403 | Permission denied | Requires board API key |
| 404 | Plugin not found | Verify the key with paperclip_list_plugins |