Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
The USPTO prosecution record for your AI. Connect once and work any U.S. patent application.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.patentreply.ai/mcp/v2在终端中运行这条命令
claude mcp add --transport http patentreply https://mcp.patentreply.ai/mcp/v2粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"patentreply": {
"url": "https://mcp.patentreply.ai/mcp/v2"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"patentreply": {
"type": "http",
"url": "https://mcp.patentreply.ai/mcp/v2"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.patentreply.ai/mcp/v2菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 patentreply.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.9.0)于19天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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](https://www.patentreply.ai/connect) · Follow the walkthrough · Documentation
Start free: one new public matter per month, no credit card. See pricing and plan features.
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.
| 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.
| Connection | Details |
|---|---|
| Hosted MCP server | https://mcp.patentreply.ai/mcp/v2 |
| Transport | Streamable HTTP |
| Authentication | OAuth sign-in; no API key |
| 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.
Install the packaged skills, commands, and MCP connection together:
claude plugin marketplace add patentreply/patentreply-mcp
claude 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.
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.
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.
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 info@patentreply.ai. 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.
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.