Skip to main content
Glama
lichman0405

PDF2ZH MCP Server

by lichman0405
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENAI_MODELYesModel identifier (e.g. anthropic/claude-opus-4-5, gpt-4o)
WORKSPACE_DIRNoShared workspace directory. Defaults to ~/.featherflow/workspace~/.featherflow/workspace
OPENAI_API_KEYYesAPI key for the provider
OPENAI_BASE_URLYesAPI base URL (e.g. https://openrouter.ai/api/v1, https://api.openai.com/v1)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
translate_pdfA

Translate a PDF file while preserving formulas and layout.

    Args:
        file: Path to the input PDF file.  Absolute paths are used
              as-is; relative paths are resolved against the shared
              workspace directory (~/.featherflow/workspace by default,
              overridable via WORKSPACE_DIR env var).
        lang_in: Source language code (e.g. "en", "auto" for auto-detect).
        lang_out: Target language code (e.g. "zh", "ja", "ko", "fr", "de").
        output_dir: Directory for output files. Defaults to the shared
                    workspace directory so that other MCP tools
                    (e.g. feishu-mcp upload_file) can access the outputs.

    Returns:
        A summary with absolute paths to the mono (translated-only) and
        dual (bilingual side-by-side) output PDF files.  These paths
        can be passed directly to feishu-mcp upload_file / upload_file_and_share.

    Environment variables that control the LLM used for translation:
        OPENAI_BASE_URL – API base URL
        OPENAI_API_KEY  – API key
        OPENAI_MODEL    – Model name
list_supported_languagesA

List language codes supported for translation.

    Returns a table of common language codes that can be used as
    lang_in or lang_out parameters.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

Only two tools with clearly distinct purposes: one lists supported languages, the other translates PDFs. No overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern: list_supported_languages and translate_pdf. No mixing of conventions.

Tool Count3/5

With only 2 tools, the server feels thin for a broader translation service, but it is scoped to a single core task. The count is borderline acceptable.

Completeness4/5

The core workflow (translating a PDF with language selection) is fully covered. Missing optional features like output format control, but no critical gaps for the stated purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources