xlide-excel-word-powerpoint-access-office-vba-mcp

Overview Schema Source Related Servers Discussions Admin

Add or remove a project reference

xlide_manage_reference

DestructiveIdempotent

Add or remove a VBA type library reference and save the file, fixing missing-library-reference errors and enabling early binding in Office projects.

Instructions

Adds or removes a type library reference in a VBA project and saves the file. Use it when xlide_analyze reports missing-library-reference, or when code needs early binding, as Dim d As Scripting.Dictionary does. Name the library: Excel, Word, PowerPoint and Access work anywhere, and on Windows any library the VBA editor's References dialog lists resolves by its description (Microsoft Scripting Runtime) or by the name code writes (Scripting), taking its GUID, version and path from this machine's registry. A name that matches several libraries is refused with the candidates. Off Windows, pass guid and version. Adding the host's own library, or removing Microsoft Forms while a UserForm exists, is refused: the first is implicit and the second stops the project compiling.

Input Schema

TableJSON Schema

Name	Required	Description
`guid`	No	For add: the library's GUID, when it is not registered on this machine. library is then the name the reference is recorded under.
`action`	Yes	'add' or 'remove'.
`library`	Yes	For add: the library's description, the name code uses, or Excel, Word, PowerPoint or Access. For remove: the name xlide_list_references reports, or the GUID.
`version`	No	For add with guid: major.minor in hexadecimal, as the registry spells it, such as 1.0 or 2.8. Empty takes the newest registered, or 1.0.
`file_path`	Yes	Absolute path to the Office file.
`allow_protected`	No	Permit saving a password-protected VBA project. Set true only after the user agrees.
`allow_invalidate_signature`	No	Permit saving a change that removes the VBA project's digital signature, where applicable. Set true only after the user agrees.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.2Sep 30, 2026

changedInput schema / properties / allow_invalidate_signature / description

Previous value: -"Ask the user first."New value: +"Permit saving a change that removes the VBA project's digital signature, where applicable. Set true only after the user agrees."

changedInput schema / properties / allow_protected / description

Previous value: -"Ask the user first."New value: +"Permit saving a password-protected VBA project. Set true only after the user agrees."

Addedv1.1.0Sep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by disclosing that the file is saved, that names resolve against the Windows registry, that ambiguous names are refused with candidates, and that adding the host's own library or removing Microsoft Forms while a UserForm exists fails. This is rich operational context an agent cannot get from readOnly/destructive hints alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and effect, then layers resolution and refusal rules. Dense but every sentence carries information; the long registry sentence is the only slightly heavy spot.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary. The description covers the mutation, platform variance, ambiguity handling, and refusal conditions, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: how the library string resolves (description, code name, or Excel/Word/PowerPoint/Access), where guid/version are needed, and that ambiguity is rejected. It enriches the schema rather than restating it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb pair (adds or removes) and resource (type library reference in a VBA project), plus the side effect of saving the file. This clearly distinguishes it from the sibling xlide_list_references, which only reads references.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use it when xlide_analyze reports missing-library-reference, or when code needs early binding') and platform guidance ('Off Windows, pass guid and version'). It does not say when to avoid this tool in favor of another sibling, so it falls short of a full when/when-not/alternatives statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server