foundry-mcp-reference

Document safe Foundry MCP workflows for editing docs without breaking heading structure.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill foundry-mcp-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-mcp-reference
Source: https://github.com/danhannah94/claymore-plugins/tree/main/foundry/skills/foundry-mcp-reference
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill foundry-mcp-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Foundry MCP users often need a clear mental model, reliable editing patterns, and warning signs for tricky operations to edit docs safely. This reference provides the core concepts, common pitfalls, and safe workflows to reason about and perform MCP actions without breaking structure or losing annotations.

Core Features & Use Cases

  • Mental model and heading-path conventions for pages and sections (get_page, create_doc, delete_doc, update_section).
  • Safe-edit workflows and pattern guidance to avoid annotation loss and structural corruption.
  • Practical guidelines for when to rewrite vs surgical edits, and how to dispatch sub-agents via MCP annotations.

Quick Start

Navigate Foundry MCP docs safely by first reading the page with get_page, then apply surgical leaf edits using update_section on the deepest heading possible while preserving annotations.

Frequently Asked Questions about foundry-mcp-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely edit Foundry MCP docs without breaking heading structure?

To safely edit Foundry MCP docs, first read the page using get_page, then apply surgical leaf edits with update_section on the deepest heading possible while preserving annotations. This safe-edit workflow prevents structural corruption and annotation loss.

What is the difference between a full rewrite and surgical edits in Foundry MCP?

Surgical edits target specific sections using update_section on the deepest heading path to preserve existing annotations, whereas full rewrites replace larger content blocks and risk structural corruption. Choose surgical edits for targeted changes and rewrites only when necessary.

How do nested-heading paths work when updating sections in Foundry MCP?

Nested-heading paths in Foundry MCP define the hierarchical structure used to locate specific sections for update_section operations. You navigate through these heading levels to apply surgical leaf edits precisely, ensuring you modify only the intended content without affecting surrounding structure.

Why do my Foundry MCP annotations disappear after updating a document?

Foundry MCP annotations disappear when using full rewrites instead of surgical edits or when failing to preserve annotation markers during update_section operations. To avoid annotation loss, always apply surgical leaf edits on the deepest heading possible and preserve existing annotation structures.

Can I use delete_doc and create_doc without corrupting my Foundry MCP page structure?

Yes, you can use delete_doc and create_doc safely by following the safe-edit workflow and understanding the mental model for Foundry MCP operations. Always verify heading paths and annotation dependencies before deleting or creating documents to maintain structural integrity.

When should I dispatch sub-agents via MCP annotations during Foundry workflows?

Dispatch sub-agents via MCP annotations when your Foundry MCP workflow requires delegated tasks within document sections. The reference provides practical guidelines for annotation handling, ensuring sub-agents are triggered correctly without disrupting the safe-edit workflow or heading structure.