Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Yakpdf MCP Server convert this article to PDF: https://example.com/blog/post"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
用于访问 Yakpdf API 的 MCP 服务器。
EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！
🌐 访问 EMCP 平台
📝 注册并登录账号
🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器
🔍 搜索或找到本服务器（bach-yakpdf）
🎉 点击 "安装 MCP" 按钮
✅ 完成！即可在您的应用中使用
✨ 零配置：无需手动编辑配置文件
🎨 可视化管理：图形界面轻松管理所有 MCP 服务器
🔐 安全可靠：统一管理 API 密钥和认证信息
🚀 一键安装：MCP 广场提供丰富的服务器选择
📊 使用统计：实时查看服务调用情况
立即访问 EMCP 平台 开始您的 MCP 之旅！
Related MCP server: FileToPDF MCP server
这是一个 MCP 服务器，用于访问 Yakpdf API。
PyPI 包名: bach-yakpdf
版本: 1.0.0
传输协议: stdio
pip install bach-yakpdfpip install -e .# 运行（uvx 会自动安装并运行）
uvx --from bach-yakpdf bach_yakpdf
# 或指定版本
uvx --from bach-yakpdf@latest bach_yakpdfpython server.py# 安装
pip install bach-yakpdf
# 运行（命令名使用下划线）
bach_yakpdf此 API 需要认证。请设置环境变量:
export API_KEY="your_api_key_here"变量名 | 说明 | 必需 |
| API 密钥 | 是 |
| 不适用 | 否 |
| 不适用 | 否 |
编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:
{
"mcpServers": {
"bach-yakpdf": {
"command": "uvx",
"args": ["--from", "bach-yakpdf", "bach_yakpdf"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}编辑 Claude Desktop 配置文件 claude_desktop_config.json:
{
"mcpServers": {
"bach-yakpdf": {
"command": "uvx",
"args": ["--from", "bach-yakpdf", "bach_yakpdf"],
"env": {
"API_KEY": "your_api_key_here"
}
}
}
}此服务器提供以下工具:
pdfGenerate a PDF from a URL or HTML string.
端点: POST /pdf
传输协议: stdio
HTTP 客户端: httpx
MIT License - 详见 LICENSE 文件。
此服务器由 API-to-MCP 工具生成。
版本: 1.0.0
Generate a PDF from a URL or HTML string.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the action ('Generate a PDF') but fails to describe any behavioral traits such as performance, error handling, rate limits, or output format. This leaves significant gaps in understanding how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's function without any unnecessary words. It is front-loaded and appropriately sized for its purpose, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (generating PDFs from varied inputs) and lack of annotations or output schema, the description is incomplete. It does not cover behavioral aspects, usage context, or output details, leaving the agent with insufficient information for effective tool invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description adds value by specifying the input sources ('URL or HTML string'), which provides context beyond the empty schema, earning a baseline score above 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Generate') and resource ('PDF'), specifying the input sources ('from a URL or HTML string'). It distinguishes what the tool does effectively, though there are no sibling tools to differentiate from, which prevents a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or any context for its application. It merely states what it does without indicating scenarios or constraints for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
pdfScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'pdf' has a clear and distinct purpose of generating PDFs from URLs or HTML strings, leaving no room for misselection by an agent.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'pdf' is simple and descriptive, and with no other tools to compare against, there are no inconsistencies in naming patterns or conventions.
A single tool is too few for a server named 'Yakpdf MCP Server', which suggests a PDF-focused domain. While the tool covers a core function, the scope feels thin and incomplete, as typical PDF servers might include additional operations like merging, splitting, or extracting text from PDFs.
The tool surface is severely incomplete for a PDF server. It only supports generating PDFs from URLs or HTML, with no coverage for other common PDF operations such as reading, editing, converting, or managing existing PDF files. This creates significant gaps that will likely cause agent failures in broader PDF-related tasks.
Turn HTML or a live URL into polished PDF and Excel files — hosted downloads, async jobs, history.
Cloud PDF generation from HTML, CSS and XSL-FO, with PDF/A and PDF/UA support.
Turn HTML or Markdown into a clean, styled PDF and get a download link.
Free HTML/URL to PDF conversion API. Convert HTML content or any URL to high-quality PDF documents. No API keys required.
