PatentReply

ai.patentreplyPublished by patentreply.aiOfficial publisherv1.9.0Updated Nov 1, 2026

The USPTO prosecution record for your AI. Connect once and work any U.S. patent application.

VerifiedStreamable HTTPWeb executableProductivity & Workflow Knowledge & Memory Business & Commerce

Server details

Identifier: ai.patentreply/patentreply
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 18, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to patentreply.ai, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.patentreply%2Fpatentreply.svg)](https://sourceweft.com/mcp/ai.patentreply%2Fpatentreply?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted MCP server that gives an AI assistant the USPTO prosecution record for a U.S. patent application, with gated drafting tools.

What you can do: Open a matter by application number and retrieve the public USPTO file wrapper, claims, Office Actions, cited references and specification
Summarize prosecution history, pending claims and changes in the application
Analyze each rejection with the claims and evidence the examiner relies on, and verify cited passages against claim text
Retrieve MPEP and other legal-authority text for the analysis
Prepare examiner interview agendas and response options with specification support
Run record QC on an uploaded draft, then generate a response document and claim listing after attorney approval
When to use it: Useful for patent practitioners and teams who want an assistant to work through a U.S. application's prosecution record: reviewing rejections, checking examiner citations, preparing interviews, or planning and drafting responses under attorney control.
Requirements: Remote Streamable HTTP endpoint with OAuth sign-in; no API key. A PatentReply account and plan are needed, and feature access and usage allowances depend on the plan. A free tier covers one new public matter per month. The first compilation of a matter can take a few minutes.

Before you install

Tool-call arguments, including any text or documents you supply, are sent to the hosted service; confidential matter information should go through the private support channel. Drafting is gated on a registered practitioner approving the plan on the PatentReply approval page, and a chat confirmation does not sign it. The service does not file with the USPTO, and it is software, not a law firm.

Installation

In SourceWeft

Open PatentReply in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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/ai.patentreply%2Fpatentreply/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": {
    "patentreply": {
      "type": "http",
      "url": "https://mcp.patentreply.ai/mcp/v2"
    }
  }
}

README

PatentReply MCP — USPTO Patent Prosecution for Claude and ChatGPT

Connect your AI to the patent file wrapper. Open a U.S. patent matter in Claude, ChatGPT, or Cursor and work with an assistant that has the prosecution record organized and indexed: claims, Office Actions, cited references, and the specification.

Review a rejection, check the examiner's citations, prepare for an interview, or develop a response plan. PatentReply supplies the record and workflow; you direct the strategy and approve the plan before response drafting.

Connect PatentReply · Follow the walkthrough · Documentation

Start free: one new public matter per month, no credit card. See pricing and plan features.

How it works

Connect once. Add the hosted Model Context Protocol (MCP) server to your AI client and approve the PatentReply sign-in.
Open a matter. Give your AI an application number. PatentReply retrieves the public USPTO file wrapper and builds the working record. The first compilation can take a few minutes.
Work through the case. Ask questions, inspect the source passages, and develop a response. An attorney approves the response plan on PatentReply before the gated drafting tools generate the response and claim listing.

After connecting, replace the bracketed text with your application number:

Open U.S. application [your application number] in PatentReply. Summarize the current claims and prosecution posture, and flag any missing or disputed record material before we discuss strategy.

What you can do

Task	Try asking your AI
Understand the prosecution history	"What changed in this application, and which claims are currently pending?"
Analyze an Office Action	"Review each rejection and show the claims and evidence the examiner relies on."
Verify a cited passage	"Show the cited paragraph of the primary reference and compare it with claim 1."
Check patent prosecution authority	"Retrieve MPEP 2143.01 and explain how it relates to this rejection."
Prepare an examiner interview	"Help me prepare an interview agenda and fallback positions for this matter."
Plan amendments and a response	"Develop response options for each rejection, with specification support for proposed amendments."
Review a draft before filing	"Give me an upload link for my response draft, then run QC against the record."

Explore the workflows and tools and walk through an Office Action review. Feature access and usage allowances depend on your plan.

Connect your AI

Client	Get started
Claude web, desktop, or mobile	Add a custom connector using the server URL, then approve the sign-in. Claude guide.
ChatGPT	Add PatentReply as a custom MCP plugin with OAuth. ChatGPT setup and compatibility URL.
Claude Code	Install the plugin below, or use the MCP-only connection.
Cursor	Add `mcp/cursor.mcp.json` to your MCP configuration. Cursor guide.
Other clients	Use a client that supports Streamable HTTP and PatentReply's OAuth flow. Connection details.

The connection guide covers authentication, first use, and troubleshooting.

Claude Code plugin

Install the packaged skills, commands, and MCP connection together:

bash

claude plugin marketplace add patentreply/patentreply-mcpclaude plugin install patentreply@patentreply

claude plugin marketplace add patentreply/patentreply-mcpclaude plugin install patentreply@patentreply

Start a Claude Code session, run /mcp, and complete the PatentReply sign-in. Then try /patentreply:status with an application number, or use ordinary language. Other commands are /patentreply:oa, /patentreply:respond, and /patentreply:interview.

The plugin already declares the hosted MCP server as patent-kb. Choose this installation or the MCP-only connection; see existing connections if you already added the endpoint manually.

Evidence and attorney control

PatentReply makes the compiled claims, Office Actions, cited references, specification, and prosecution history available to your AI. Record citations use pkb:// verification addresses into the stored matter. Legal-authority tools retrieve MPEP and other supported authority text for the analysis.

The workflow checks the record before drafting and surfaces missing source material, unresolved citations, and disputed claim text. A source address lets you inspect the evidence; the attorney still evaluates the conclusion.

Response planning and drafting are separate stages. A plan revision is submitted for a registered practitioner's approval on the PatentReply approval page. After approval, the hosted service generates the response Word document and the 37 CFR 1.121 claim listing for attorney review. A confirmation in chat does not sign the plan, and PatentReply does not file papers with the USPTO.

Public repository and service

This is the official public repository for PatentReply setup instructions, registry metadata, and the Claude plugin. The hosted service is operated by Patent Agentic LLC.

Resource	Location
Connection instructions	docs/connect.md
Workflows, skills, and tool overview	docs/workflows.md
Office Action review walkthrough	examples/office-action-review.md
Pricing, records, and privacy questions	docs/faq.md
Claude plugin contents	plugin/
MCP Registry metadata	server.json, server name `ai.patentreply/patentreply`
Glama ownership metadata	glama.json
Maintenance and discovery checklist	docs/maintainers.md

The plugin/ tree is generated from the PatentReply build and replaced on release. Report changes through an issue so they can be made in the source build. See maintenance guidance.

Privacy and support

PatentReply receives the arguments your AI sends in its tool calls, including any text or documents you choose to supply through the workflow. It does not independently read your conversation history, client memory, or local files. PatentReply does not use your matters to train models. Your AI provider's handling of the conversation is governed separately.

Privacy · Security · Terms · Pricing

For connection problems or documentation feedback, open an issue or email [email protected]. Include the client and the error message; send confidential matter information through the appropriate private support channel.

PatentReply is software, not a law firm. The registered practitioner remains responsible for every filing. See the FAQ for scope and limits.

License

The files outside plugin/ are released under the MIT License; see LICENSE for its scope. The generated plugin/ tree is proprietary as stated in its manifest. The hosted service is governed by its Terms.

[M8ven Score]

Source: README.md at commit 7b1b576

Tools

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

v1.9.0LatestOct 18, 2026

Score

75% 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
Declare a license in the repository or the registry entry.