How can an AI agent control Microsoft Office?

An MCP-compatible AI agent can use DCC-MCP to inspect shared Office runtime capabilities and route supported document work to the owning application adapter. The agent selects the correct application instance or integration, discovers available tools, and reads their parameter definitions before acting and checking the result. These typed tools declare their inputs, outputs, and parameter types.

Microsoft Office MCP and Microsoft Office CLI

The Microsoft Office MCP endpoint and Microsoft Office CLI workflow share the same DCC-MCP adapter and tool catalog. Use dcc-mcp-cli with --dcc-type office to limit tool searches to Microsoft Office. Tools declare their inputs, outputs, and parameter types so arguments can be checked before a call.

dcc-mcp-cli search --query "inspect the registered Office runtime and supported application routes" --dcc-type office

What can an AI agent do in Microsoft Office?

• inspect the registered Office runtime and supported application routes.
• prepare one bounded document operation through the owning adapter.
• verify the saved document or rendered output in the target application.

Capabilities change with the adapter version and loaded Skills. Search and describe tools first instead of guessing current tool names from this page.

Safe operating flow

1. Install and follow the public dcc-mcp Skill.
2. Inspect the existing CLI, adapter, and live hosts; obtain consent before installing software or changing system state.
3. Use health, dcc-types, and list to verify the Gateway and target instance.
4. Search and describe tools for the actual Microsoft Office task, then follow every returned next_step.
5. Make one bounded change and verify it through host state, files, previews, logs, or rendered output.

dcc-mcp-cli health
dcc-mcp-cli dcc-types
dcc-mcp-cli list

Copyable prompt

Use the dcc-mcp Skill to connect to my Microsoft Office session. Inspect the existing CLI, adapter, and live instance first; ask before installing software or changing system state. Search for and describe typed tools related to "prepare one bounded document operation through the owning adapter", then follow every returned next_step. Do not delete, overwrite, or publish existing work. Make the smallest verifiable change, then check the result against this requirement: "verify the saved document or rendered output in the target application". Report the instance, tool, result, and evidence path.

Current availability and official source

The shared Office runtime has a separate office application route; it is not among the 38 adapter identifiers observed with CLI 0.20.39. Application-specific support remains explicit; use the owning PowerPoint, Word, Excel, or Outlook repository for its current status and verify the live instance before operating.

• Microsoft Office adapter repository: source of truth for installation, compatibility, host-specific capabilities, and troubleshooting.
• All AI + DCC control guides: return to every public application and pipeline integration.
• Agent workflow: shared discovery, call, validation, and diagnostic steps.

This page describes the shared Agent workflow. Each integration's repository owns its installation, API, and compatibility details.