Yowes: An MCP Server for Generating Teacher Documents by Country—Start with Read-Only Tools to Scope Out Coverage

Yowes is a headless Python MCP server for generating teacher-identity-related documents—including employment verification letters, teacher IDs, teaching licenses, payslips, and more—covering 13 countries. It provides no validation or verification capability of its own; it only renders output as PNG images. So before deciding to use it, you must be clear that your purpose is legitimate document generation (e.g., testing, templates, demos), not forging documents that imitate real institutions' credentials.

Who It's For

• Developers or testers who need to render teacher-type document images (PNG) in batches by country/school—e.g., for document templates, UI demos, or sample data.
• Environments that already have a stdio MCP client and Python 3.10+ installed locally; the Pillow and mcp dependencies are installed automatically along with the package.
• When it's not suitable: the official repository only describes "generating realistic teacher documents," with no statements about authorization, legal use, or misuse prevention. If your goal involves files that could be used as genuine credentials, the evidence contains no support for such use, and unknown risks must be assessed by you.
• The scope of language and internationalization support is not stated in the evidence; check the repository yourself.

First Attempt in 3 Minutes

The main path is installing from the pre-built wheel with pip:

pip install dist/yowes_doc_generator-0.1.0-py3-none-any.whl

Note: this installs the wheel file from the local dist directory, so you need to clone the repository first (the official repo also offers two secondary options—editable install from source and uvx—which this article does not cover). After installation, register it in your MCP client configuration:

"mcpServers": {
  "yowes": {
    "command": "yowes-mcp",
    "args": []
  }
}

Once configured, yowes will block over stdio waiting for MCP requests. For your first attempt, it's recommended to call only the read-only tool list_countries_tool, which lists the 13 supported countries. This is a side-effect-free call; if the client returns the country list, the server is connected properly.

Success signal: the client's tool list shows the three tools list_countries_tool, list_schools(country), and generate_documents(...), and list_countries_tool returns the country list.

Actually generating files (generate_documents(...)) is a local write operation: it renders documents as PNGs and writes them by default into the output/ directory, returning the file paths. This is not a networked write, but it does create files on local disk; if the file contents are sensitive, decide for yourself whether to keep or delete them.

Use Cases

Case 1: Confirm the supported scope. After starting the server, call list_countries_tool in the client to see the list of 13 countries; then call list_schools(country) with a given country to see the available schools in that country. The evidence only states that these two tools exist and their basic signatures; the specific fields of the returned data are not described in the evidence.

Case 2: Generate a teacher document image. Call generate_documents(...), which accepts one or more document requests at a time; the server renders them as PNGs and returns the paths of the generated files. Finding the images in the output/ directory means success. Note: the evidence does not give the tool's full parameter structure (how to pass country, school, and document type); before calling, check the parameter documentation in the repository rather than constructing parameters by guesswork.

Usage Boundaries

• Read/write nature: list_countries_tool and list_schools(country) are query-type tools; generate_documents(...) writes PNG files to the local output/ directory. The official project provides no path for revoking already-generated files; local files must be cleaned up manually.
• Credential requirements: the evidence does not state that any API key or login credentials are needed, nor whether personal information such as name or email must be provided; unknowns are subject to the actual parameter definitions in the repository.
• Privacy and compliance: generating "realistic teacher credentials" can be misused, and the official documentation does not provide the specific content of usage restrictions or disclaimers—this point is unconfirmed. Read-only tools merely mean no write operations are performed; that does not mean zero risk. Whether the server goes online and which local data it reads are not stated in the evidence.
• How it runs: it blocks over stdin/stdout waiting for MCP requests; when running from source, the corresponding command is python mcp_server.py.