Common Paper

com.commonpaperPublished by commonpaper.comOfficial publisherv1.0.1Updated Oct 24, 2026

Create, send, negotiate, sign, and track contracts with Common Paper.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote Common Paper MCP server that lets an assistant search, draft, send, sign, track and manage your organization's contracts in plain English.

What you can do
  • Search and count agreements, including by counterparty, status, deal value and end date
  • Draft and send agreements such as NDAs and CSAs, then void, reassign, resend or download them as PDFs and get shareable links
  • Inspect signers, renewals and financial details of agreements
  • Create and update templates for NDA, CSA, DPA, PSA, Partnership, BAA, LOI, Software License, Design Partner and Pilot
  • Publish custom terms and build custom cover page templates
  • Walk through account onboarding and create a starter set of templates
When to use it
Useful when you work with Common Paper for contract lifecycle work and want an assistant to answer questions about existing agreements, prepare drafts, or manage templates without leaving the chat. Best for teams already on Common Paper who want plain-language contract queries and drafting.
Requirements
A Common Paper account and an MCP client with OAuth support; sign-in happens through OAuth with no API key to copy. The optional plugin needs Claude Cowork, Claude Code, Cursor, Grok Build or Gemini CLI. The REST fallback needs curl and network access to api.commonpaper.com, and custom terms or custom templates must be enabled for your organization.
Before you install
The assistant acts as the signed-in user and can send emails, void agreements, reassign recipients and resend signature requests; the bundled plugin asks for confirmation before such actions and creates drafts by default, but a bare connector may not. If the REST fallback is used, an API key may be minted and stored at a local config path. Contract text is sent to Common Paper's service.

Installation

In SourceWeft

  1. Open Common Paper 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.commonpaper%2Fcontracts/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": {
    "common-paper": {
      "type": "http",
      "url": "https://api.commonpaper.com/mcp"
    }
  }
}

README

Common Paper MCP server and AI plugins

Query, create, and manage your contracts in Common Paper from your AI assistant, in plain English. Common Paper runs a remote MCP server that works with any MCP client, including GitHub Copilot, VS Code, Claude, Cursor, and ChatGPT.

This repo also packages the server as a plugin for Claude Cowork, Claude Code, Cursor, Grok Build, and Gemini CLI. The plugin bundles two things:

  • The Common Paper MCP connector (https://api.commonpaper.com/mcp). You sign in with your Common Paper account through OAuth, so there's no API key to copy or store.
  • A Common Paper skill that teaches how Common Paper works: agreement statuses, the Cover Page + Standard Terms model, safe defaults (every agreement starts as a draft), template parameters for each agreement type, the rules for porting contract text into custom terms without altering it, and a guided onboarding flow for new accounts.

For a few things the connector doesn't cover yet (filtering by company name or end date, uploading Word files as custom terms, and creating a brand-new account), the skill falls back to the Common Paper REST API.

What you can do

  • Count and search: "How many signed NDAs do we have?" / "Do we have a contract with Acme?"
  • Send agreements: "Draft an NDA to [email protected] from [email protected]" (the assistant creates a draft, shows you the link, and sends only when you confirm)
  • Manage agreements: void, reassign the recipient, resend the signature email, download the PDF, get a shareable link
  • Financial questions: "What's our largest CSA by deal value?"
  • Renewals: "Which contracts expire in the next 90 days?"
  • Signers: "Who signed the deal with Microsoft?"
  • Templates: create and update NDA, CSA, DPA, PSA, Partnership, BAA, LOI, Software License, Design Partner, and Pilot templates
  • Custom agreements: publish custom terms and build custom cover page templates
  • Onboarding: "Set up my Common Paper account" walks through ten quick questions and creates a starter set of templates

Example prompts

  1. How many signed contracts do we have, and how many are still waiting on the other side?
  2. Do we have an active NDA with Northwind? If not, draft one to [email protected] from me.
  3. List every agreement that ends in the next 90 days as a table with counterparty, type, and end date.
  4. Create a CSA template with Delaware law, a 1x fees liability cap, and net-30 annual invoicing.
  5. Set up my Common Paper account.

Use with any MCP client

  • Server URL: https://api.commonpaper.com/mcp
  • Transport: Streamable HTTP
  • Auth: OAuth. Clients that support dynamic client registration connect automatically, and you sign in with your Common Paper account. No API key needed.

VS Code and GitHub Copilot

Add this to .vscode/mcp.json:

json
{  "servers": {    "common-paper": {      "type": "http",      "url": "https://api.commonpaper.com/mcp"    }  }}

Start the server from the file or the MCP servers list, then sign in to Common Paper when prompted.

OpenAI Codex CLI

bash
codex mcp add common-paper --url https://api.commonpaper.com/mcpcodex mcp login common-paper

The first command adds the server to ~/.codex/config.toml. The second opens a browser so you can sign in to Common Paper.

Setup for other assistants (ChatGPT, Cursor, Notion, Perplexity, and more) is in Connecting Common Paper to other AI assistants.

Install as a plugin

The plugin adds a skill on top of the MCP server with Common Paper workflows and safe defaults.

Claude Cowork

Install Common Paper from the plugin directory, then connect when prompted and sign in to Common Paper.

Claude Code

Install from the plugin directory with /plugin, or add this repo as a marketplace directly:

bash
claude plugin marketplace add CommonPaper/ai-pluginclaude plugin install commonpaper@commonpaper

Then run /mcp, choose common-paper, and sign in to Common Paper.

Cursor

Install Common Paper from the Cursor Marketplace, or add this repo to your team marketplace (Dashboard > Plugins & MCPs). Then open the Customize page, find common-paper under MCP servers, and sign in to Common Paper.

To try a local copy, clone this repo into ~/.cursor/plugins/local/commonpaper.

Grok Build

Add this repo as a marketplace and install the plugin. --trust lets Grok attach the bundled Common Paper connector.

bash
grok plugin marketplace add CommonPaper/ai-plugingrok plugin install commonpaper --trustgrok plugin enable commonpaper

Then sign in to Common Paper when Grok prompts you to connect common-paper.

Gemini CLI

bash
gemini extensions install https://github.com/CommonPaper/ai-plugin

Then run /mcp auth common-paper in Gemini CLI and sign in to Common Paper.

Upgrading from the standalone skill

If you previously installed CommonPaper/claude-skill, you can remove it after installing the plugin. If the plugin ever needs an API key for the REST fallback, it copies a key saved by the old skill to ~/.config/commonpaper/cp-api-token automatically.

Requirements

  • A Common Paper account
  • Any MCP client with OAuth support, or for the plugin: Claude Cowork, Claude Code, Cursor, Grok Build, or Gemini CLI
  • For the REST fallback only: curl and network access to api.commonpaper.com. Custom terms and custom templates must be enabled for your organization to use those features.

Security and privacy

  • The server uses OAuth. Your assistant acts as the Common Paper user who signed in and can only see that user's organization.
  • With the plugin, the assistant confirms before anything that sends an email or changes a live agreement (send, void, reassign, resend, invite), and creates agreements as drafts by default.
  • If the REST fallback needs an API key, the plugin mints one for the signed-in user with the connector (or asks you for one), asks whether to keep it for future sessions, stores it at ~/.config/commonpaper/cp-api-token with owner-only permissions (deleting it at the end of the task if you said not to keep it), and never prints it in chat.
  • Contract text ported into custom terms is kept character-for-character. The assistant verifies the stored text after writing and never "fixes" typos or punctuation on its own.
  • Privacy policy: https://commonpaper.com/privacy-policy/ (questions: [email protected])

Troubleshooting

ProblemFix
The Common Paper tools aren't connectedCowork: Customize > Connectors > Common Paper > Connect. Claude Code: run /mcp, choose common-paper, and sign in. Cursor: open the Customize page, find common-paper under MCP servers, and connect. Gemini CLI: run /mcp auth common-paper. Codex CLI: run codex mcp login common-paper. VS Code: start common-paper from .vscode/mcp.json or the MCP servers list. Other clients: connect https://api.commonpaper.com/mcp from the client's MCP settings.
An agreement you expect is missingThe API only covers agreements sent by your organization. Agreements you received from another organization aren't included.
"You've reached your plan limit" on a new accountUsually means your email address isn't verified yet. Verify it, then try again.
404 on custom terms or custom templatesThe feature isn't enabled for your organization. Contact Common Paper support.
REST fallback fails with a network errorYour environment can't reach api.commonpaper.com directly. The assistant will fall back to what the connector supports.
Search by company name is slow on a large accountWithout the REST fallback, the assistant has to page through agreements. Allow network access to api.commonpaper.com so it can filter server-side.

Support

  • Help center: Common Paper and LLMs
  • Bugs and feature requests: open an issue in this repository
  • For account or connection problems, contact Common Paper support through the help center with the name of the client you're using and a screenshot of the error

Repo contents

.claude-plugin/plugin.json          Plugin manifest (Claude, Grok Build).claude-plugin/marketplace.json     Lets this repo be added as a marketplace (Claude).cursor-plugin/plugin.json          Plugin manifest (Cursor).cursor-plugin/marketplace.json     Lets this repo be added as a marketplace (Cursor).grok-plugin/marketplace.json       Lets this repo be added as a marketplace (Grok Build).mcp.json                           Common Paper MCP connector (Claude, Grok Build)mcp.json                            Common Paper MCP connector (Cursor)gemini-extension.json               Extension manifest and connector (Gemini CLI)registry/server.json                MCP Registry entry (com.commonpaper/contracts)skills/commonpaper/SKILL.md         Core skillskills/commonpaper/references/      REST API, templates, custom terms, onboarding details

License

MIT

Source: README.md at commit abe5ec7

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.1LatestOct 6, 2026
  2. v1.0.0Sep 24, 2026

Score

85% 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
  • License10 pts