MCP办公文档 是 AI Skill Hub 本期精选MCP工具之一。综合评分 7.5 分,整体质量较高。我们推荐使用将其纳入你的 AI 工具库,帮助提升工作效率。
MCP办公文档 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
MCP办公文档 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
# 方式一:通过 Claude Code CLI 一键安装
claude skill install https://github.com/ForLegalAI/mcp-ms-office-documents
# 方式二:手动配置 claude_desktop_config.json
{
"mcpServers": {
"mcp----": {
"command": "npx",
"args": ["-y", "mcp-ms-office-documents"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
# 安装后在 Claude 对话中直接使用 # 示例: 用户: 请帮我用 MCP办公文档 执行以下任务... Claude: [自动调用 MCP办公文档 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入:"列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"mcp____": {
"command": "npx",
"args": ["-y", "mcp-ms-office-documents"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
| Document Type | Tool | Highlights |
|---|---|---|
| 📊 **PowerPoint** | create_powerpoint_presentation | Title, section & content slides · 4:3 or 16:9 format · Custom templates · Author metadata, footer text & slide numbers · Inline markdown (**bold**, *italic*, ~~strikethrough~~, code) · Table column alignment |
| 📝 **Word** | create_word_from_markdown | Write in Markdown, get a .docx · Headers, lists, tables, links, formatting · Superscript, subscript & highlighted text · Table column alignment, borderless tables & proportional column widths · Multi-paragraph table cells |
| 📈 **Excel** | create_excel_from_markdown | Markdown tables → .xlsx · Formulas & cell references supported |
| 📧 **Email** | create_email_draft | HTML email drafts (.eml) · Subject, recipients, priority, language |
| 🗂️ **XML** | create_xml_file | Well-formed XML files · Auto-validates & adds XML declaration if missing |
All tools accept an optional file_name parameter. When provided, the output file will use that name (without extension) instead of a randomly generated identifier.
Bonus — Dynamic Templates:
first_name, promo_code)..docx files with {{placeholders}}. Each template becomes an AI tool. Placeholders support full Markdown.Output options: - Local — Files saved to the output/ folder - Cloud — Upload to S3, Google Cloud Storage, Azure Blob, or MinIO and get a time-limited download link
---
Get up and running in 3 steps:
cp .env.example .env
The defaults work out of the box — files will be saved locally to output/.
The server is configured through environment variables in your .env file.
| Variable | Description | Default |
|---|---|---|
DEBUG | Enable debug logging (1, true, yes) | _(off)_ |
API_KEY | Protect the server with an API key (see Authentication below) | _(disabled)_ |
UPLOAD_STRATEGY | Where to save files: LOCAL, S3, GCS, AZURE, MINIO | LOCAL |
SIGNED_URL_EXPIRES_IN | How long cloud download links stay valid (seconds) | 3600 |
RUN_BLOCKING_BY_ASYNCIO_THREAD_ENABLED | Offload blocking tool work to a thread pool, keeping the event loop free for health probes & concurrent requests | true |
RUN_BLOCKING_MAX_WORKERS | Maximum concurrent worker threads for blocking tool calls | 4 |
<details> <summary><strong>🔐 Authentication</strong></summary>
Set API_KEY in your .env to require an API key for all requests:
API_KEY=your-secret-key
Clients can send the key in any of these headers:
| Header | Format |
|---|---|
Authorization | Bearer your-secret-key |
Authorization | your-secret-key |
x-api-key | your-secret-key |
Leave API_KEY empty or unset to allow all requests without authentication.
</details>
<details> <summary><strong>☁️ AWS S3 Storage</strong></summary>
Set UPLOAD_STRATEGY=S3 and provide:
| Variable | Description | Required |
|---|---|---|
S3_BUCKET | S3 bucket name | ✅ Always |
AWS_ACCESS_KEY | AWS access key ID | ⚠️ See below |
AWS_SECRET_ACCESS_KEY | AWS secret access key | ⚠️ See below |
AWS_REGION | AWS region (e.g., us-east-1) | ⚠️ See below |
Credential modes:
AWS_ACCESS_KEY, AWS_SECRET_ACCESS_KEY, and AWS_REGION. Recommended for simple setups.AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY environment variables~/.aws/credentials)aws sso login) — useful for local developmentIn this mode only S3_BUCKET is required; region is resolved automatically.
</details>
<details> <summary><strong>☁️ Google Cloud Storage</strong></summary>
Set UPLOAD_STRATEGY=GCS and provide:
| Variable | Description |
|---|---|
GCS_BUCKET | GCS bucket name |
GCS_CREDENTIALS_PATH | Path to service account JSON (default: /app/config/gcs-credentials.json) |
Mount the credentials file via docker-compose.yml volumes.
</details>
<details> <summary><strong>☁️ Azure Blob Storage</strong></summary>
Set UPLOAD_STRATEGY=AZURE and provide:
| Variable | Description |
|---|---|
AZURE_STORAGE_ACCOUNT_NAME | Storage account name |
AZURE_STORAGE_ACCOUNT_KEY | Storage account key |
AZURE_CONTAINER | Blob container name |
AZURE_BLOB_ENDPOINT | _(Optional)_ Custom endpoint for sovereign clouds |
</details>
<details> <summary><strong>☁️ MinIO / S3-Compatible Storage</strong></summary>
Set UPLOAD_STRATEGY=MINIO and provide:
| Variable | Description | Default |
|---|---|---|
MINIO_ENDPOINT | MinIO server URL (e.g., https://minio.example.com) | _(required)_ |
MINIO_ACCESS_KEY | Access key | _(required)_ |
MINIO_SECRET_KEY | Secret key | _(required)_ |
MINIO_BUCKET | Bucket name | _(required)_ |
MINIO_REGION | Region | us-east-1 |
MINIO_VERIFY_SSL | Verify SSL certificates | true |
MINIO_PATH_STYLE | Use path-style URLs (recommended for MinIO) | true |
Make sure the bucket exists and your credentials have PutObject/GetObject permissions.
</details>
<details> <summary><strong>🏥 Performance & Health Probes</strong></summary>
The server exposes health-check endpoints that Kubernetes (or any orchestrator) can use for liveness/readiness probes:
| Endpoint | Purpose |
|---|---|
GET /health | Basic liveness check |
GET /readiness | Readiness check |
Thread-pool offloading: By default (RUN_BLOCKING_BY_ASYNCIO_THREAD_ENABLED=true), all blocking document-generation work is dispatched to a bounded thread pool (RUN_BLOCKING_MAX_WORKERS threads, default 4). This keeps the asyncio event loop free to respond to health probes and handle concurrent requests — critical for Kubernetes deployments where blocked probes lead to pod restarts.
Set RUN_BLOCKING_BY_ASYNCIO_THREAD_ENABLED=false only for local debugging or to rule out threading-related issues.
</details>
---
AI Skill Hub 为第三方内容聚合平台,本页面信息基于公开数据整理,不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后,再部署至生产环境,并做好必要的安全评估。
✅ MIT 协议 — 最宽松的开源协议之一,可自由商用、修改、分发,仅需保留版权声明。
经综合评估,MCP办公文档 在MCP工具赛道中表现稳健,质量良好。如果你已有明确的使用需求,可以直接上手体验;如果还在评估阶段,建议对比同类工具后再做决策。
| 原始名称 | mcp-ms-office-documents |
| 原始描述 | 开源MCP工具:MCP server providing tools to create Ms Office documents like presentations, ema。⭐25 · Python |
| Topics | mcpdocxemlpython |
| GitHub | https://github.com/ForLegalAI/mcp-ms-office-documents |
| License | MIT |
| 语言 | Python |
收录时间:2026-05-25 · 更新时间:2026-05-30 · License:MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。
选择 Agent 类型,复制安装指令后粘贴到对应客户端