DocAuto

io.github.gzucobPublished by GitHub account gzucobv0.3.0Updated Oct 24, 2026

Model Context Protocol server for the DocAuto document-generation API.

VerifiedSTDIODesktop onlyFiles & Storage

Server details

Identifier: io.github.gzucob/docauto-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account gzucob for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.gzucob%2Fdocauto-mcp.svg)](https://sourceweft.com/mcp/io.github.gzucob%2Fdocauto-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

DocAuto is a local MCP server that connects an assistant to the DocAuto document-generation API.

What you can do: It exposes the DocAuto document-generation API to an MCP client over stdio, so an assistant can work with that service through tool calls. The registry entry names no individual tools, so the exact operations are not documented here. It runs as a local process on the user's machine and is marked desktop only.
When to use it: Consider it when you already use the DocAuto document-generation API and want an assistant to reach it from a desktop MCP client. It is not useful if you do not use DocAuto or need a browser-based client.
Requirements: A local runtime able to run the PyPI package docauto-mcp, for example uvx. It is desktop only and not available as a web executable. The manifest declares no authentication, environment variables or headers, but the underlying DocAuto API may still require its own account or credentials.

Before you install

The manifest declares no authentication and no environment variables, so any credentials the DocAuto API needs would have to be supplied some other way; check how they are stored before installing. Document generation may send your content to the DocAuto service, and generated documents may be created or overwritten. No tool list is published, so verify what the server can do before granting it access.

Installation

In SourceWeft

Open DocAuto in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.