RoughSketch is also a remote MCP (Model Context Protocol) server. Point an AI assistant at this URL and it can search, read, draw, and edit the same Google Drive sketches you open in the editor.
https://roughsketch.app/mcpOpens Claude with the endpoint filled in; you confirm it there, then press Connect and sign in with Google.
By hand: Settings, then Connectors, then Add custom connector.
Run this once, then approve the browser prompt.
claude mcp add --transport http roughsketch https://roughsketch.app/mcpThese install the connector for you, after asking permission.
If a button does nothing, your editor is not registered to handle its install links. Add the endpoint URL by hand instead.
Anything that speaks MCP over streamable HTTP works. Give it the endpoint URL and sign in with Google when it asks.
In Claude Code, run /mcp — the server should be listed as connected, with ten tools. In Cursor, look under Settings, then Tools and MCP.
Anywhere else, just ask for something and watch it use the tools:
List my RoughSketch sketches — use MCP tools.
Paste one in. The first is the fastest way to prove the connection is live.
What RoughSketch sketches do I have?
Sketch my app's signup flow and save it to RoughSketch.
Open my signup flow sketch and add a password-reset branch.
Tidy up my signup flow — align the boxes and space them evenly.
Show me the signup flow as an image and say what you would change.
Only sketches. RoughSketch asks Google for the narrow drive.file scope, which grants access to files you created or opened through RoughSketch and nothing else — the rest of your Drive stays invisible to the assistant, and to RoughSketch.
Unlike the editor, the assistant never reaches Google Drive itself. Its requests come to our server, which reads and writes the sketch on your behalf; the contents stay in memory for that one request — what the assistant asked for goes back to it, and from there it is the assistant operator's to handle under their policy, not ours. Asking for a preview is what leaves something behind: we render the sketch to an image, and Cloudflare's edge cache holds that image, or — when the assistant asks for the sketch's sections instead — that list, which holds each section's name (the first line of its largest text, or “Region N” where it has none), bounding box, element count and element ids, for up to 24 hours, keyed to the file and its last-modified time (and, for images, the requested region, elements and size). When a full render fails, a marker recording the sketch's size in bytes is held — seconds in the ordinary case, up to 6 hours when the sketch is too large to render — so we do not retry a render that cannot succeed. Nothing is served from the cache until Google Drive confirms the requester can already open the file. The Privacy Policy has the full account.
Connecting is its own authorization, separate from being signed in here: you approve it inside the client, and it stores a record on our side — your email address, plus the Google refresh and access tokens issued for that connection — so the assistant keeps working without re-authorizing every time. Those tokens are encrypted under a key belonging to that one connection; we hold no key of our own for it, and unwrap it only with a credential the assistant sends. That record expires 30 days after you authorize it. Removing the connector in your assistant deletes that record as soon as the client revokes the connection's refresh token — the standard request, which not every client sends. If yours doesn't, email us and we will delete it. Revoking at your Google account instead stops the connection working but leaves the record in place until it expires.
Edits to a sketch's contents carry a write precondition — the assistant hands back the modification time it last read, and the edit is refused if the sketch changed since. Renaming and trashing carry no such check, so an assistant can trash a sketch it never read; that lands in your Google Drive trash and you restore it from there.