Programmable document workflows
Macros & MCP
Make document capabilities callable beyond the editor surface.
Explore source ↗Capability
VBA-compatible macro runtime and Model Context Protocol tools expose document and reporting operations to scripts, automation, and AI agents.
- 01
Document macro runtime
- 02
VBA compatibility direction
- 03
MCP document tools
- 04
MCP reporting tools
How it composes
From intent
to working system.
Command
Document and report operations expose a controlled automation surface.
Runtime
Macros or MCP handlers resolve commands against scoped services.
Document
Automation operates on the same model used by editors and reports.
Policy
Hosts control files, tools, permissions, and execution boundaries.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package ProEdit.Mcp.Documents --prerelease<PackageReference Include="ProEdit.Vba.Runtime" Version="VERSION" /><PackageVersion Include="ProEdit.Vba.Runtime" Version="VERSION" />services.AddProEditDocuments();services.AddProEditMcpDocuments();
// Expose scoped document commands through the MCP host.await app.RunAsync();Modules in this capability
Use one layer.
Compose the rest.
Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.