MCP

MCP document generation for AI agents

OfficeMaker, operated by AI Build Group Ltd, provides a Model Context Protocol (MCP) server for document generation. Agents can fetch live schemas, analyse payload gaps and create native Word, Excel and PowerPoint files without copying an API key into the public free tier.

Direct answer

An MCP create tool takes documentJson as an object after get_minimal_schema. The free REST API is different: document_type, file_name and document_json as a string. The public free MCP server covers create, preview, schema and gap analysis. Merge and edit are paid.

What MCP document generation is

MCP is a protocol for giving AI agents tools. OfficeMaker’s MCP tools wrap the same schema-led document service used by the REST API and the website: create a native Office file from a structured payload.

The public free MCP server is intentionally narrow: create, preview-oriented flows, schema discovery and gap analysis. It does not expose merge, edit, macros or conversion.

An MCP tool request is not a REST body. On the free REST API, create uses snake_case document_type, file_name and document_json, and document_json is a string. On MCP, the create tool takes documentJson as an object and the client calls get_minimal_schema before create. Both paths return a native Office file. The three downloads under Examples are files created on 22 October 2026: a DOCX proposal, an XLSX forecast with formulas, and a six-slide PPTX.

Word, Excel and PowerPoint via MCP

  • Word: structured DOCX from a schema-valid payload
  • Excel: structured XLSX, including tables and formulas when specified
  • PowerPoint: structured PPTX slides from the PowerPoint schema
  • Gap analysis before create so agents can fix missing fields

How agents should call it

Discover tools from the MCP server, fetch the schema for the document type, fill the payload, optionally run gap analysis, then create. Prefer structured fields over dumping prose into a single untyped blob.

Paid MCP on the document-service host can add organisation connections and the full create / merge / edit set. That surface is licensed, not implied by the free server.

In a wider automation stack, OfficeMaker MCP is the document-generation tool behind an MCP-capable environment. Zapier, Make or n8n can still orchestrate the business process. See AI workflow automation tools and MCP workflow tools.

Client-specific setup guides are available for ChatGPT, Claude Desktop, Cursor, Windsurf, Cline, VS Code, Claude Code, Goose and Nimbalyst. Each guide is grounded in the client’s current official MCP documentation; OfficeMaker does not claim that every client exposes identical authentication or permission behaviour.

Evidence behind the MCP claims

OfficeMaker publishes both the live document-service interface and public implementation examples. Client-specific guides link to the official MCP documentation for each host instead of assuming Claude Desktop, Cursor, VS Code and other clients configure MCP identically.

The public GitHub examples also make the entity relationship machine-readable outside the OfficeMaker domain: OfficeMaker is the document-execution layer; workflow and agent products remain the orchestration/client layer.

Claim. OfficeMaker exposes MCP document-generation tools for compatible agent clients.

Mechanism. The client discovers the OfficeMaker tools, fetches a live schema, builds structured state and invokes the document service.

Evidence. Developer hub

Limitation. Client authentication, transport and tool-permission behaviour depends on the MCP host and OfficeMaker service tier.

Limitations

Free MCP does not write to Salesforce or run tenant macros. Published starter repositories are listed on the developer page.

Open developer resources · Create an account · Free tier OpenAPI (JSON)

Questions

What is MCP document generation?
MCP document generation is OfficeMaker’s Model Context Protocol surface for AI agents. Agents can fetch live Word, Excel and PowerPoint schemas, run gap analysis, and create native Office files from structured payloads without embedding an API key on the public free tier.
Does the free MCP server edit existing Office files?
No. The public free MCP server supports create, preview-oriented flows, schema discovery and gap analysis. It does not expose merge, edit, macros or document conversion. Those verbs are available on the paid document-service API.
Where is the OpenAPI description?
The free-tier OpenAPI document is published at https://free.officemaker.ai/gpt/openapi.json. Authenticated developers can also open the document-service portal at docs.officemaker.ai/portal for schema-led guides.
Can agents create Word, Excel and PowerPoint via REST?
Yes. REST create endpoints accept structured JSON for Word (DOCX), Excel (XLSX) and PowerPoint (PPTX). Fetch the matching schema first, then POST a payload. The free host is https://free.officemaker.ai; paid tenants use the document-service host with authentication.
Can an AI agent create Word files through MCP?
Yes. After initialize and tools/list, fetch the Word schema, optionally run gap analysis, then create a native DOCX. The public free MCP server does not merge or edit an existing Word file.
Can an agent create Excel through MCP?
Yes. The same schema-then-create pattern produces a native XLSX. Formulas and charts are included when the payload specifies them.
Can an AI agent create PowerPoint through MCP?
Yes. Fetch the PowerPoint schema and create a native PPTX. Website CMS tools live on a separate operator MCP and are not mixed into tenant document generation.