Agent MCP Directory

PatchDesign.AI: MCP server, CLI and agent surfaces

Yes: PatchDesign.AI runs a public MCP server at patchdesign.ai that listed 5 tools to a client with no credentials on 4 November 2026. Examples: quote_patch, design_patch, edit_patch. It speaks streamable-http, protocol 2025-06-18. Open servers are readable by any agent; writes still depend on each tool.

Fact sheet

CompanyPatchDesign.AI
Domainpatchdesign.ai
CategoryProductivity (assigned by this directory from the registry description)
MCP serverVerified (No authentication)
Ora scorenone: Ora returned no cached score for patchdesign.ai when asked on 5 November 2026
Company found throughthe GitHub MCP Registry; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://patchdesign.ai/api/mcp
How it was foundlisted in the GitHub MCP Registry; the official MCP Registry
Transportstreamable-http
HTTP status200
Protocol version2025-06-18
Serverpatchdesign-ai 1.0.1
Capabilitiestools, resources
Tools5
Resources1
Prompts0
Connected4 November 2026, 20:03 UTC
Handshake time2,222 ms over 1 attempt

Tools listed

5 tools

  • quote_patch
  • design_patch
  • edit_patch
  • order_link
  • sign_in_link

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:58:52Z https://patchdesign.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 3339 ms
  • 20:04:01Z https://patchdesign.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 2222 ms

Authentication

Auth typeNo authentication

The sign-in route, step by step

  1. Send the handshake to https://patchdesign.ai/api/mcp over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
  2. Send tools/list, then resources/list and prompts/list if the capabilities name them.
  3. Send no token. The connector sent none and the server answered, so any MCP client can read this list.
  4. Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for PatchDesign.AI. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)Not checked: the domain is not in the shared crawl for this edition.
agents.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: ai.patchdesign/patch-designer
GitHub MCP RegistryYes
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.