Vibe Patent

ai.vibepatentPublished by vibepatent.aiOfficial publisherv1.0.0Updated Nov 1, 2026

Idea to patent draft in minutes, with attorney filing.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that turns an invention idea into a patent draft, with attorney filing offered as a follow-on service.

What you can do
  • Turns an idea into a patent draft, per the provider's description.
  • Connects over a remote streamable HTTP endpoint with OAuth sign-in.
  • No tool list is published, so the exact drafting, editing or filing actions an assistant can call are not documented here.
  • Filing is described as handled with an attorney rather than by the assistant.
When to use it
Worth considering when you want an assistant to help move from a rough invention idea toward a patent draft and possibly a filing, instead of drafting from scratch in a chat.
Requirements
A remote endpoint at api.vibepatent.ai; no local package or runtime. OAuth authentication is required, so a Vibe Patent account is needed. No environment variables or headers are declared.
Before you install
Patent applications involve confidential invention details, which will be sent to a third-party service. Filing with an attorney likely involves fees and legal engagement terms; confirm pricing and who reviews the draft before relying on it. The tool set is undocumented, so verify what the assistant can actually do.

Installation

In SourceWeft

  1. Open Vibe Patent 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/ai.vibepatent%2Fvibe-patent/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": {
    "vibe-patent": {
      "type": "http",
      "url": "https://api.vibepatent.ai/functions/v1/api-v1-mcp-server"
    }
  }
}

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

1
  1. v1.0.0LatestNov 1, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • 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.