Vizspect

Give your AI assistant
a pen in Visio

Vizspect connects Claude Code, Cowork, Codex, and other MCP-enabled AI assistants to Microsoft Visio — so the assistant you already use can draw and edit USPTO-compliant patent figures and other types of drawings, live on your own machine.

Request beta access

For Windows 11 · Requires Microsoft Visio

How it works

A real figure drawn in Visio through Vizspect — no edits, not sped up.

The missing link between AI and Visio — not another drawing app

Vizspect is a smart MCP server — the bridge between the AI assistant you already use and Microsoft Visio, with a patent draftsperson’s rules built in. You talk to your assistant the way you always do; it uses Vizspect to actually draw and edit the figure in your live Visio document.

It doesn’t replace your assistant, and it doesn’t replace Visio — it connects them. Every shape, connector, and reference numeral lands with patent-grade precision, on your machine, in the document you’re already working in.

Built for patent practice — and capable of far more wherever clean, rule-driven Visio diagrams matter.

Your AI assistant

Claude Code, Cowork, Codex — cloud or local, any MCP client

Vizspect

~50 precise drawing tools, with USPTO house style enforced

Microsoft Visio

Your live document — figures appear and update as you watch

From install to first figure

1

Install & connect

Install on Windows 11. A tray app runs the local server and registers it with Claude Code and Codex automatically; other MCP clients connect with a URL.

2

Open your document

Open Visio. Vizspect attaches to your live session — it never launches a hidden copy or touches anything you didn’t ask it to.

3

Ask your assistant

Tell your assistant what to draw. Watch the figure build in Visio, then refine by conversation or by hand — you’re always in control.

The figures your assistant can build

Describe the figure in plain language and your assistant builds it in Visio through Vizspect, one element at a time — each one placed, numbered, and styled to USPTO conventions.

01

Apparatus & block diagrams

Boxes, connectors, and a labeled system extent — placed on a fine grid and wired up with obstacle-aware connectors that route around components, not through them.

  • Components placed precisely — never sloppy auto-layout
  • Connectors route around your boxes, not through them
  • Reference numbers assigned and styled for you
  • Always within USPTO margins, on every page

Claude — “draw a block diagram of the imaging system — an optical sensor, signal processor, frame buffer, system controller, memory, and output interface — with reference numerals.”

02

Flowcharts & decision trees

Stadium START/END, decision diamonds, and YES/NO branches that leave from different vertices with collision-aware labels — the conventions a patent flowchart needs, handled for you.

  • Decision diamonds, branches, and START/END done right
  • YES/NO labels placed clear of every line
  • Steps numbered in order, automatically
  • Crisp at any size or print resolution

Claude — “make a flowchart: detect an event, check whether it’s valid, then process and store it — otherwise discard it.”

03

UI mockups & interfaces

Device frames with labeled screen elements, buttons, and fields — the kind of interface figure that’s fiddly to align by hand, laid out cleanly in seconds.

  • Device frames with neatly labeled elements
  • Reference numerals with clean, non-crossing leaders
  • Sharp 1.0pt black line art at any zoom
  • Consistent, legible labels throughout

Claude — “mock up an analysis workstation — a sidebar with Overview, Reports, and Settings, a chart panel, and a Run button.”

04

Swimlanes & complex flows

Multi-lane process figures built in a single pass — dotted lane headers with underlined foreign element numbers, same-height cross-lane steps, and START/END, all numbered to convention.

  • Multiple lanes laid out in a single step
  • Clear cross-lane flow with tidy arrows
  • Every element numbered without collisions
  • Ask once, then refine by conversation

Claude — “build a swimlane across Intake, Analysis, Review, and Output: receive data, validate, score the event, then record the result.”

It checks your figures, too

Vizspect can read what’s already on the page — every shape, label, and reference numeral — so your assistant can audit and cross-check your figures against the specification, not just draw them.

Numeral consistency

Claude — “list every reference numeral in the figures and flag any that appear in the spec but not the drawings, or vice versa.”

Build the numeral table

Claude — “list each labeled element across all figures and what it’s called, so I can assemble the reference-numeral table.”

Claim coverage

Claude — “does the flowchart include every step recited in the method claim? Tell me what’s missing.”

Pre-filing check

Claude — “lint the figures for off-margin shapes, crossed leaders, and numerals that drifted off their element before I export.”

Far beyond the basics

The same precise toolset handles the rest of the figures a specification needs — and general-purpose Visio diagrams too.

Swimlane charts

Cross-lane flow with numbered lane headers

Timing diagrams

Clocked waveforms from a pattern string

Org charts

Hierarchies with consistent connectors

Network diagrams

Nodes, links, and labeled topology

Process maps

Multi-step processes with clean routing

Architecture tiers

Layered systems and component stacks

…and most any other clean black-and-white line diagram, just by asking.

The rules of the drawing, handled

Vizspect knows the USPTO drawing rules and your house style, so every figure your assistant produces comes out consistent — without you policing every line and numeral.

USPTO house style, automatic

Black-and-white line art, ALL-CAPS Arial text, and 1.0pt strokes — with 37 CFR 1.84 margins enforced on every placement, portrait or landscape.

Collision-aware reference numerals

Numerals and leader lines slide along the target’s edge until nothing overlaps and no line is crossed — or the tool refuses and says exactly what’s blocking it.

Works with your AI assistant

A smart MCP server for Claude Code, Cowork, Codex, and other Model Context Protocol clients — cloud or local. Any model with tool-calling support can drive it. (The ChatGPT app isn’t supported yet.)

Lint & geometry checks

A read-only check flags out-of-margin shapes, overlaps, text overflow, crossed leaders, and numerals that drifted off a moved element — a pre-render gate before you file.

Edit live, alongside you

Work on the same document as your assistant. Every write re-reads the figure first, and destructive edits require explicit assertions — so your hand edits aren’t silently overwritten.

Runs entirely on your machine

The server runs locally and talks to your own copy of Visio. Your client documents never go to the cloud and never leave your computer.

Not just for patent lawyers

Vizspect was built to satisfy one of the strictest drawing standards there is — USPTO patent figures. That same precision makes it a fast, exacting drawing companion for anyone who works in Visio.

Engineers & architects

System, network, and architecture diagrams with exact placement and clean, obstacle-aware routing — not approximate auto-layout.

Technical writers & docs teams

Consistent, legible figures for manuals, specifications, and standards — generated and updated straight from your AI assistant.

Anyone who lives in Visio

Skip the fiddly drag-and-align. Describe the diagram in plain language and get precise, lint-checked Visio output you can keep editing.

Vizspect

Ready to draw faster?

Vizspect is in private beta for patent practitioners. Get in touch to join — pricing will be announced at launch.

For Windows 11. Requires Microsoft Visio and a supported AI assistant.