RoughSketch

What RoughSketch MCP server does

The RoughSketch MCP server gives an AI agent access to RoughSketch sketches stored in the user's own Google Drive. Its stated scope is limited to three operations: listing sketches, reading sketches, and creating sketches. This makes it relevant for workflows where an agent needs to find an existing sketch, inspect its contents, or add a new sketch to the connected Drive.

The server is centered on the relationship between RoughSketch and Google Drive. The available description does not identify other storage providers, design applications, project-management systems, or collaboration platforms. It also does not describe editing, deleting, moving, sharing, exporting, or searching sketches beyond the stated listing capability.

Tools and capabilities

The RoughSketch MCP server supports these capabilities:

• List RoughSketch sketches in the user's Google Drive.
• Read RoughSketch sketches from that Drive.
• Create RoughSketch sketches in that Drive.

The material does not provide formal tool names, argument schemas, return formats, or examples. As a result, an agent integration should be evaluated against the server's actual MCP tool definitions rather than assumed operation names or parameters.

The RoughSketch MCP server is a fit for an agent that needs a narrow sketch-storage interface. For example, an agent could enumerate sketches before selecting one to read, or create a new sketch as the output of a conversation. Whether it can update an existing sketch, work with folders, preserve metadata, or handle concurrent changes is not established by the provided information.

No claims can be made from the available material about how Google Drive access is authorized or which Drive account is used. The description specifies the user's own Google Drive, but does not explain consent screens, tokens, scopes, account selection, or credential storage. Those details should be confirmed in the project's setup instructions before deployment.

The source material also does not identify an MCP transport, runtime, package manager, operating-system requirement, configuration file, environment variable, license, or supported MCP client. Consequently, this listing should be treated as a capability reference rather than a complete installation guide. Confirm those implementation details at the project source before selecting the server for production use.