Paperform

com.paperformPublished by paperform.comv1.0.1Updated Nov 6, 2026

Create beautiful forms that do more. Take payments, get documents signed, automate the rest.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote Paperform MCP server that lets an assistant work with Paperform's form builder for forms that take payments, collect signatures and automate follow-up.

What you can do
  • Build and manage Paperform forms, including styled, multi-purpose forms.
  • Handle payment collection and document signing within forms.
  • Set up automation for what happens after a form is submitted.
  • No tool list is published, so the exact operations available are not documented here.
When to use it
Worth adding when you already use Paperform and want an assistant to help create or maintain forms, payment flows, signature requests or post-submission automations without switching tools.
Requirements
A remote MCP endpoint at api.paperform.app, connected over streamable HTTP. Authentication is OAuth and required, so you need a Paperform account and must approve the connection. No environment variables or headers are declared.
Before you install
The connection is authorized through OAuth and grants the assistant access to your Paperform account; review the scopes shown at consent. Forms can take payments and collect signatures, so changes may affect real money and legally relevant documents. No tool list is published, so what the assistant can read or change is unclear until you connect.

Installation

In SourceWeft

  1. Open Paperform in the dashboard and add it to a workspace.
  2. Connect the required 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.paperform%2Fpaperform/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "paperform": {
      "type": "http",
      "url": "https://api.paperform.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestNov 6, 2026
  2. v1.0.0Nov 3, 2026

Score

83% 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
  • Documentation15 pts
  • 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.