PreviewSend

com.previewsendPublished by previewsend.comOfficial publisherv1.0.0Updated Oct 24, 2026

Deploy a built website from your coding agent and share one client review link.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

PreviewSend lets a coding agent deploy a built website and share a single client review link.

What you can do
  • Deploy a built website from the coding agent.
  • Share one client review link for the deployed site.
  • No tool list is published, so the exact operations are not documented here.
When to use it
Useful when an agent finishes building a site and you want to publish it quickly and hand a client a single review link instead of hosting it yourself.
Requirements
Remote MCP endpoint at previewsend.com over streamable HTTP. A PreviewSend account and a deploy key created in the account settings, sent as a bearer token in the Authorization header.
Before you install
The Authorization header carries a secret deploy key that grants deploy access; keep it out of shared logs and prompts. Deploying publishes a site that others can reach through the review link.

Installation

In SourceWeft

  1. Open PreviewSend in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.previewsend%2Fpreviewsend/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "previewsend": {
      "type": "http",
      "url": "https://previewsend.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 12, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.