factory-mcp-docs-scan

Identify available documentation-focused MCP servers during BLUEPRINT and IMPLEMENT commands.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-mcp-docs-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-mcp-docs-scan
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-mcp-docs-scan
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-mcp-docs-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When running BLUEPRINT or IMPLEMENT commands, agents often waste time attempting to query unavailable documentation MCPs or miss relevant official docs sources, leading to reliance on outdated training data for design and implementation tasks. This Skill eliminates that guesswork by automatically identifying which docs-focused MCPs are connected and available to use.

Core Features & Use Cases

  • Automatic MCP Discovery: Introspects the agent's own tool registry to find all connected MCP servers without manual configuration or external checks.
  • Explicit Allowlist Filtering: Only surfaces docs-focused MCPs from a predefined allowlist, ignoring general-purpose tools that do not provide documentation lookup.
  • Mandatory Per-Invocation Banner: Emits a clear, single-line banner at the start of every relevant command invocation listing available docs sources, with a fallback message for offline or greenfield use.
  • Use Case: When starting a new feature build with the IMPLEMENT --build command, the skill immediately tells you if the context7 or AWS Knowledge MCPs are available, so you can pull official, up-to-date documentation instead of relying on stale training data.

Quick Start

Invoke the factory-mcp-docs-scan skill at the start of any BLUEPRINT or IMPLEMENT command to receive a clear list of available documentation MCPs you can consult for your current design or implementation task.

Frequently Asked Questions about factory-mcp-docs-scan

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

FAQPage Schema
How do I check which MCP servers are available for documentation lookup during an agent build task?

To check available documentation MCP servers, the skill introspects the agent's connected tool registry and applies an explicit allowlist to surface only docs-focused sources for your build task. It filters out general-purpose tools automatically without requiring external checks.

Why does my agent rely on outdated training data instead of querying official documentation during implementation?

Your agent relies on outdated training data when it lacks awareness of connected documentation MCPs. This skill solves that by emitting a mandatory per-invocation banner at the start of BLUEPRINT and IMPLEMENT commands, explicitly listing available official docs sources to query.

Can I use this MCP discovery skill without any manual configuration or external dependencies?

Yes, you can use this skill without manual configuration. It has zero external dependencies and automatically discovers connected MCP servers by introspecting the agent's own internal tool registry, providing a seamless setup experience for design workflows.

What happens if no documentation MCPs are connected when running a BLUEPRINT command?

If no documentation MCPs are connected, the skill provides an offline fallback message within its mandatory per-invocation banner. This ensures the agent knows no docs sources are available and gracefully falls back for greenfield use instead of failing.

Does this tool filter out general-purpose MCPs to ensure only documentation sources are surfaced?

Yes, this tool filters out general-purpose MCPs using a predefined allowlist. It explicitly ignores non-documentary tools during introspection, ensuring agents only attempt to query relevant, official, and up-to-date documentation sources for design and build tasks.