SKILL.md Extension · v1.0

mcp_dependencies

A SKILL.md frontmatter block that declares every MCP server a workflow depends on. Enables Cromus to simulate token overhead, detect configuration drift, and enforce pre-execution governance before a single tool call is made.

Why declare MCP dependencies?

Cost simulation

Every MCP transport adds overhead tokens per call. Without a declaration, the simulator cannot account for this cost and your forecasts will be understated.

Drift detection

Tool schemas change. When schema_version is declared, check_mcp_drift compares it against the live server and flags breaking changes before they hit production.

Structural governance

Skills that call tools without declaring mcp_dependencies receive a Structural Gaps penalty in their Croms score — the same signal that flags missing budget declarations.

Field reference

fieldtyperequireddescription
server_namestringYesUnique identifier for the MCP server (alphanumeric, hyphens, underscores)
transportenumYesstdio | sse | streamable_http
toolsstring[]YesList of tool names called by this skill (at least one)
authenumYesnone | api_key | oauth
fallbackenumYesfail | degrade | skip — behavior when server is unavailable
estimated_calls_per_runintegerYesExpected number of tool calls per skill execution (drives overhead calculation)
schema_versionstringNoSemver of the tool schema; enables drift detection via check_mcp_drift

Transport overhead

Extra input tokens and latency added per MCP call by transport type. Cromus multiplies these by estimated_calls_per_run and adds to each simulation run's totals.

transportextra tokens / callextra latency / callnotes
stdio+200+150 msLocal process, lowest latency
sse+250+80 msHTTP streaming, near-real-time
streamable_http+300+120 msStandard HTTP, best compatibility

Example SKILL.md

A GitHub Issue Manager skill declaring its MCP dependency with full field coverage, including schema_version for drift detection.

---
name: GitHub Issue Manager
version: 1.0.0
execution_target: Claude Managed Agents
estimates:
  token_input: 3200
  token_output: 1200
  runs_per_month: 50
mcp_dependencies:
  - server_name: github-mcp
    transport: stdio
    tools:
      - create_issue
      - list_pull_requests
      - update_issue
    schema_version: "1.0.0"
    auth: oauth
    fallback: fail
    estimated_calls_per_run: 4
---

Fallback semantics

fail

The workflow terminates immediately if the MCP server is unreachable. Use for non-optional integrations where partial execution is worse than no execution.

degrade

The workflow continues but marks affected outputs as incomplete or estimated. Use for optional enrichment steps (analytics, logging, notifications).

skip

The workflow silently skips the MCP step and proceeds. Use only when the tool call is genuinely optional with no downstream dependency.

Check your MCP server

Paste your server manifest URL or JSON and get a scored readiness report across auth, tool quality, error contracts, rate limits, and directory compliance.

Run MCP Server Check