Skip to main content
Glama
shawnwei512

doc-distillation-mcp

by shawnwei512
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DISTILL_HTML_DIRNoHTML output directory~/Documents/蒸馏文稿
DISTILL_OBSIDIAN_DIRNoObsidian vault directory~/Documents/obsidian

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
distill_urlA

Distill content from a URL into HTML article + Obsidian note.

Supports:

  • Feishu documents (feishu.cn, larkoffice.com)

  • Webpages (any HTTP/HTTPS URL)

  • PDF files (.pdf URLs)

  • Video/podcast URLs (YouTube, Bilibili, etc. - returns guidance)

Output:

  • HTML distillation article saved to ~/Documents/蒸馏文稿/

  • Obsidian note saved to ~/Documents/obsidian/{subdir}/

For large documents, set async_mode=true and poll with get_distill_status.

distill_fileA

Distill content from a local file into HTML article + Obsidian note.

Supports:

  • PDF files (.pdf)

  • HTML files (.html, .htm)

  • Text/Markdown files (.txt, .md)

  • Audio/Video files (.mp3, .m4a, .wav, .mp4 - returns guidance)

Output:

  • HTML distillation article saved to ~/Documents/蒸馏文稿/

  • Obsidian note saved to ~/Documents/obsidian/{subdir}/

get_distill_statusA

Check the status of an async distillation task.

Returns the task status, progress, and result (if completed). Poll this periodically until status is 'completed' or 'failed'.

list_distillationsA

List all completed distillations.

Returns a list of completed distillation tasks with metadata. Use get_distill_status with a task_id to get full content.

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.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: distill_url and distill_file differ by input source (remote vs local), while get_distill_status and list_distillations handle task monitoring and history respectively. No overlapping responsibilities.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern: distill_url, distill_file, get_distill_status, list_distillations. The verbs appropriately reflect the action, and naming is uniform.

Tool Count5/5

4 tools is a well-scoped set for a distillation service. It covers initiation (URL/file), status checking, and listing results without excess or deficiency.

Completeness4/5

Core distillation workflow is covered: create via URL/file, check async status, and list completed tasks. Minor gaps like lack of delete/cancel or retrieval of a specific completed task's content via a dedicated getter, but agents can work around using get_distill_status.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources