previewdrop

MCPcommunity
v0.1.13UnknownMITUpdated 2d agonpmGitHub

CLI for PreviewDrop — live preview environments for every branch. Any Dockerfile, any stack.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4Downloads/wk
2d agoLast update
Reads these credentials
  • PREVIEWDROP_API_KEYAPI keyoptional

    PreviewDrop API key. Optional: without it the server still starts and lists its tools, and each tool explains how to connect. Create one at previewdrop.dev/dashboard/settings or run `npx previewdrop…

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.1.13
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface14 tools · 2 privileged
Security scan✓ Cleanv0.1.13 · 1d agoHow well does this scan work?
EvalsNone
IndexedSep 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

14 tools · 2 privileged
Statically extracted from the published packagev0.1.13 · 1d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_accountGet the authenticated PreviewDrop account info (email, plan, tenant name)

Get the authenticated PreviewDrop account info (email, plan, tenant name)

No input schema was published for this tool.

list_projectsList all PreviewDrop projects in the account

List all PreviewDrop projects in the account

No input schema was published for this tool.

list_deploymentsList deployments, optionally filtered by project, branch, or status

List deployments, optionally filtered by project, branch, or status

No input schema was published for this tool.

get_deploymentGet details of a specific deployment by ID

Get details of a specific deployment by ID

No input schema was published for this tool.

deployTrigger a new preview deployment for a project

Trigger a new preview deployment for a project

No input schema was published for this tool.

destroy_deploymentprivilegedStop and destroy a deployment by ID

Stop and destroy a deployment by ID

No input schema was published for this tool.

redeployRedeploy an existing deployment by ID (same project + branch)

Redeploy an existing deployment by ID (same project + branch)

No input schema was published for this tool.

get_build_logsFetch build logs (nixpacks / Dockerfile output) for a deployment

Fetch build logs (nixpacks / Dockerfile output) for a deployment

No input schema was published for this tool.

get_runtime_logsFetch runtime (container stdout/stderr) logs for a deployment

Fetch runtime (container stdout/stderr) logs for a deployment

No input schema was published for this tool.

create_projectAdd a repository as a PreviewDrop project. GitHub (default) needs the GitHub App installed on the repo owner's account — if not, use get_github_app_install_url first. GitLab and Bitbucket need the provider connected once in the dashboard under Settings → Integrations.

Add a repository as a PreviewDrop project. GitHub (default) needs the GitHub App installed on the repo owner's account — if not, use get_github_app_install_url first. GitLab and Bitbucket need the provider connected once in the dashboard under Settings → Integrations.

No input schema was published for this tool.

get_github_app_install_urlprivilegedReturns the GitHub URL where the user must install the PreviewDrop GitHub App. Call this when create_project returns a 403 about the App not being installed.

Returns the GitHub URL where the user must install the PreviewDrop GitHub App. Call this when create_project returns a 403 about the App not being installed.

No input schema was published for this tool.

get_project_env_varsGet the environment variable keys configured for a project. Values are masked (shown as ***) — use this to see what vars are set without exposing secrets.

Get the environment variable keys configured for a project. Values are masked (shown as ***) — use this to see what vars are set without exposing secrets.

No input schema was published for this tool.

set_project_env_varsMerge environment variables into a project. Existing vars not in the payload are kept. Values are encrypted at rest.

Merge environment variables into a project. Existing vars not in the payload are kept. Values are encrypted at rest.

No input schema was published for this tool.

deploy_repoPRIMARY TOOL — call this immediately for any "preview", "deploy", "get a URL", or "share my project" request.

PRIMARY TOOL — call this immediately for any "preview", "deploy", "get a URL", or "share my project" request.

No input schema was published for this tool.

14 of 14 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

CLI for PreviewDrop — live preview environments for every branch. Any Dockerfile, any stack.

Keywords
previewdroppreviewpreview-environmentpreview-environmentsephemeral-environmentbranch-previewpr-previewreview-appdeploymentdockergithub-appstagingdevopscli
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-17 — observed resolution, not a publisher declaration.

60 packages resolved · 8 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

91 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+79 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in git & code hosting