Skip to content

papersign-mcp-server.md

Latest commit

 

History

History
30 lines (24 loc) · 1.8 KB

papersign-mcp-server.md

File metadata and controls

30 lines (24 loc) · 1.8 KB
Raw

Papersign MCP Server

Category: Business & Commerce – MCP Servers
Tags: e-signature, document-automation

Overview

Papersign MCP Server exposes Papersign’s e-signature and document workflow capabilities through the Model Context Protocol (MCP). It is designed to let MCP-compatible chat or AI clients interact with Papersign to manage document signing workflows directly from within those clients.

  • MCP Server URL: https://mcp.pipedream.net/v2
  • Provider / Platform: Pipedream Connect
  • Use case: Integrate e-signature workflows (preparing, sending, tracking signatures) into MCP-enabled applications and chat clients.

Features

  • MCP-compatible e-signature server – Provides a Papersign-backed MCP server endpoint for use with any compatible client.
  • Static server URL – Uses a single static URL (https://mcp.pipedream.net/v2) that works across all clients.
  • Client-agnostic integration – Designed to be added to different chat or AI clients that support MCP.
  • Authentication at configuration time – Authentication is handled when you add the server to your chosen application/client.
  • Document signing workflows (from item description)
    • Prepare documents for electronic signatures.
    • Send documents out for signing.
    • Track the status of document signatures.
  • Configuration documentation – A full configuration page (linked from the app) explains how to connect and use the server from supported clients.

Getting Started

  • Add the MCP server URL https://mcp.pipedream.net/v2 to your MCP-compatible app or chat client.
  • Authenticate when prompted during setup.
  • Refer to the platform’s configuration page for detailed setup steps.

Pricing

The provided content does not include any pricing or plan information for the Papersign MCP Server.