What they did
Uhrmeister builds Filently, which files documents into a user's existing Google Drive folders. An MCP server had sat on the team's list for a while. On a Saturday Uhrmeister spent about fifteen minutes brainstorming the idea with Claude, and on the Sunday let Claude Code build a working prototype with little guidance and no real back and forth. The prototype had tools to list documents waiting for review, file a document into the suggested folder, suggest a name and folder, list every folder in Drive, and show a filing history. The team then spent the following week turning it into something they would let near users' contracts and IDs.
How it went
Uhrmeister calls the prototype surprisingly good. The shipped version, live in Claude's connector directory, cut the folder listing tool (too slow for big archives and it would expose every folder name) and the filing history tool (not reliable yet). The week went to an activity log that shows when Claude filed something, a page to disconnect AI apps, hard limits (no deletes, no reading document contents), security work and a privacy policy update. In-chat onboarding was dropped because files attached in Claude could not reach the server. No user numbers yet.
Worth knowing
A weekend prototype was not the same as a shippable connector: most of the effort went into permissions, auditing and cutting tools that leaked too much. Claude's directory policy also led them to remove a tool that asked users how they found the product. The post is by the founder and promotes Filently.