📦

Ms Office Documents

MCP server providing tools to create Ms Office documents like presentations, emails, spreadshhets and word docs (pptx, docx, eml, xlsx)

0 installs

14 stars

11 forks

Trust: 58 — Fair

Devtools

Installation

npx mcp-ms-office-documents

Ask AI about Ms Office Documents

I know everything about Ms Office Documents. Ask me about installation, configuration, usage, or troubleshooting.

0/500

Loading tools...

Reviews

Documentation

📄 MCP Office Documents Server

Let your AI assistant create professional Office documents — PowerPoint, Word, Excel, emails & XML — with a single prompt.

💡 What is this?

This is an MCP (Model Context Protocol) server that runs in Docker and gives AI assistants (like Claude, Cursor, or any MCP-compatible client) the ability to generate real Office files on demand.

Just ask your AI to "create a sales presentation" or "draft a welcome email" — and it will produce a ready-to-use file for you.

No coding required. Install, connect, and start creating.

✨ Features at a Glance

Document Type	Tool	Highlights
📊 PowerPoint	`create_powerpoint_presentation`	Title, section & content slides · 4:3 or 16:9 format · Custom templates
📝 Word	`create_word_from_markdown`	Write in Markdown, get a `.docx` · Headers, lists, tables, links, formatting
📈 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:

📧 Reusable Email Templates — Define parameterized email layouts in YAML. Each becomes its own tool with typed arguments (e.g., first_name, promo_code).
📝 Reusable Word Templates — Create .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

🚀 Quick Start

Get up and running in 3 steps:

1. Download the compose file

curl -L -o docker-compose.yml https://raw.githubusercontent.com/dvejsada/mcp-ms-office-docs/main/docker-compose.yml

Already cloned the repo? Skip this step — docker-compose.yml is already there.

2. Set up your environment

cp .env.example .env

The defaults work out of the box — files will be saved locally to output/.

3. Start the server

docker-compose up -d

✅ Done! Your MCP endpoint is ready at: http://localhost:8958/mcp

⚙️ Configuration

The server is configured through environment variables in your .env file.

Basic Settings

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`

🔐 Authentication

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.

☁️ AWS S3 Storage

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:

Explicit credentials — Set all three of AWS_ACCESS_KEY, AWS_SECRET_ACCESS_KEY, and AWS_REGION. Recommended for simple setups.
AWS default credential chain — Leave the credential variables unset and boto3 will automatically discover credentials from the standard chain:
- AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY environment variables
- Shared credential / config files (~/.aws/credentials)
- AWS SSO sessions (aws sso login) — useful for local development
- IRSA (IAM Roles for Service Accounts) — for AWS EKS deployments
- ECS container credentials / EC2 instance metadata (IMDSv2)
In this mode only S3_BUCKET is required; region is resolved automatically.

☁️ Google Cloud Storage

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.

☁️ Azure Blob Storage

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

☁️ MinIO / S3-Compatible Storage

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.

🎨 Custom Templates

You can customize the look of generated documents by providing your own templates.

Static Templates

Place files in the custom_templates/ folder:

Document	Filename	Notes
PowerPoint 4:3	`custom_pptx_template_4_3.pptx`
PowerPoint 16:9	`custom_pptx_template_16_9.pptx`
Word	`custom_docx_template.docx`
Email wrapper	`custom_email_template.html`	Base it on `default_templates/default_email_template.html`

Dynamic Email Templates

Create reusable, parameterized email layouts that your AI can fill in automatically.

📧 How to set up dynamic email templates

1. Create config/email_templates.yaml:

templates:
  - name: welcome_email
    description: Welcome email with optional promo code
    html_path: welcome_email.html  # must be in custom_templates/ or default_templates/
    annotations:
      title: Welcome Email
    args:
      - name: first_name
        type: string
        description: Recipient's first name
        required: true
      - name: promo_code
        type: string
        description: Optional promotional code (HTML formatted)
        required: false

2. Create the HTML file in custom_templates/welcome_email.html:

<!DOCTYPE html>
<html lang="en">
<head><meta charset="UTF-8" /></head>
<body>
  <h2>Welcome {{first_name}}!</h2>
  <p>We're excited to have you on board.</p>
  {{{promo_code_block}}}
  <p>Regards,<br/>Support Team</p>
</body>
</html>

How it works:

Each template becomes a separate AI tool at startup
Standard email fields (subject, to, cc, bcc, priority, language) are added automatically
Use {{variable}} for escaped text, {{{variable}}} for raw HTML

Dynamic Word (DOCX) Templates

Create reusable Word documents with {{placeholders}} that support full Markdown formatting.

📝 How to set up dynamic DOCX templates

1. Create config/docx_templates.yaml:

templates:
  - name: formal_letter
    description: Generate a formal business letter
    docx_path: letter_template.docx  # must be in custom_templates/ or default_templates/
    annotations:
      title: Formal Letter Generator
    args:
      - name: recipient_name
        type: string
        description: Full name of the recipient
        required: true
      - name: recipient_address
        type: string
        description: Recipient's address
        required: true
      - name: subject
        type: string
        description: Letter subject
        required: true
      - name: body
        type: string
        description: Main body of the letter (supports markdown)
        required: true
      - name: sender_name
        type: string
        description: Sender's name
        required: true
      - name: date
        type: string
        description: Letter date
        required: false
        default: ""

2. Create a Word document with placeholders and save as custom_templates/letter_template.docx:

{{date}}

{{recipient_name}}
{{recipient_address}}

Subject: {{subject}}

{{body}}

{{sender_name}}

How it works:

Each template becomes a separate AI tool at startup
Placeholders can be in the document body, tables, headers, and footers
Placeholder values support full Markdown (bold, italic, lists, headings…)
The original font from the placeholder location is preserved

🎯 Word style requirements for custom templates

For proper formatting, make sure these styles exist in your .docx template:

Category	Styles
Headings	Heading 1 – Heading 6
Bullet lists	List Bullet, List Bullet 2, List Bullet 3
Numbered lists	List Number, List Number 2, List Number 3
Other	Normal, Quote, Table Grid

Tip: Customize these styles (font, size, color, spacing) in your template — the server will use your styling.

🔌 Connecting Your AI Client

Point your MCP-compatible client to the server endpoint:

http://localhost:8958/mcp

Examples for popular clients:

Claude Desktop

Add to your Claude Desktop MCP config:

{
  "mcpServers": {
    "office-documents": {
      "url": "http://localhost:8958/mcp"
    }
  }
}

LibreChat

Add the server to your librechat.yaml configuration under mcpServers:

mcpServers:
  office-documents:
    type: streamableHttp
    url: http://mcp-office-docs:8958/mcp

Note: If LibreChat and this server run in the same Docker network, use the container name (mcp-office-docs) as the hostname. If they run separately, use http://localhost:8958/mcp instead.

To place both services on the same network, add a shared network in your docker-compose.yml:

services:
  mcp-office-docs:
    # ...existing config...
    networks:
      - shared

  librechat:
    # ...existing config...
    networks:
      - shared

networks:
  shared:
    driver: bridge

Cursor / Other MCP Clients

Use the SSE/streamable HTTP transport and set the endpoint URL to:

http://localhost:8958/mcp

If you have authentication enabled, add the API key header as required by your client.

🤝 Contributing

Contributions are welcome! If you'd like to help improve this project:

Fork the repository
Create a branch for your feature or fix (git checkout -b my-feature)
Commit your changes (git commit -m "Add my feature")
Push to your branch (git push origin my-feature)
Open a Pull Request

Whether it's a bug report, a new feature idea, documentation improvement, or a code contribution — all input is appreciated. Feel free to open an issue to start a discussion.