All tools

word_create

Documents · macOS · Windows

Effect: write (strongest supported action). Status: gated.

Gated means the tool requires an installed app, a connected account, permission, or runtime availability. Check those requirements on the listed platform before using it.

macOS

Purpose

Creates a new Word (.docx) document at `path` with the given text content (and an optional title rendered as the heading). Requires confirm=true — called without it, returns a preview of what will be written instead of creating the file. The path must be somewhere Local MCP can write; Desktop/Documents/Downloads may need a one-time Files-and-Folders grant (System Settings → Privacy & Security → Files and Folders). Returns {created, path}. For a OneDrive or Google Drive path use onedrive_write_file / gdrive_write_file; to append to an existing doc use word_append, to read one word_read.

Required inputs

Permissions and confirmation

Explicit confirmation parameter: inspect the schema and tool description before any real call. The documentation example keeps confirm false. Obtain user authorization before performing the action.

Full input schema — macOS
{
  "properties": {
    "confirm": {
      "description": "Must be true to create",
      "type": "boolean"
    },
    "content": {
      "description": "Document text content",
      "type": "string"
    },
    "path": {
      "description": "Output path for the .docx file",
      "type": "string"
    },
    "title": {
      "description": "Document title (optional)",
      "type": "string"
    }
  },
  "required": [
    "path",
    "content"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "confirm": false,
  "content": "Meeting agenda: review the launch checklist.",
  "path": "/Users/demo/Documents/meeting-notes.docx"
}

Windows

Purpose

Creates a new Word (.docx) document with the given content.

Required inputs

Permissions and confirmation

Explicit confirmation parameter: inspect the schema and tool description before any real call. The documentation example keeps confirm false. Obtain user authorization before performing the action.

Full input schema — Windows
{
  "properties": {
    "confirm": {
      "description": "Must be true to create the file",
      "type": "boolean"
    },
    "content": {
      "description": "Text content. Each line becomes a paragraph.",
      "type": "string"
    },
    "path": {
      "description": "Absolute path for the new .docx file",
      "type": "string"
    },
    "title": {
      "description": "Document title (optional)",
      "type": "string"
    }
  },
  "required": [
    "path",
    "content"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "confirm": false,
  "content": "Meeting agenda: review the launch checklist.",
  "path": "C:\\Users\\demo\\Documents\\meeting-notes.docx"
}