/**
 * Workflow `mcp:` reference resolution (issue #1208 Stage 1).
 *
 * A step / sub-step `mcp: [name, ...]` reference resolves against the workflow's top-level
 * `mcp_servers` definitions (the portable, bundled defaults). An unresolved name fails fast at load
 * time — never a silent drop. The runtime.yaml override layer (`order.md:110` runtime > workflow >
 * error) is additive and lands in a later stage; here the workflow-bundled definitions are the
 * resolution source. Pre-existing inline step `mcp_servers` definitions (deprecated, maintained)
 * keep working and win over a reference on a name collision, so an explicit inline override is not
 * shadowed by a bundled default.
 */
import type { McpServerConfig } from '../../../core/models/index.js';
export declare function resolveWorkflowMcpReferences(stepName: string, refs: readonly string[] | undefined, definitions: Record<string, McpServerConfig> | undefined, inline: Record<string, McpServerConfig> | undefined, stepPath: readonly PropertyKey[]): Record<string, McpServerConfig> | undefined;
//# sourceMappingURL=workflowMcpReferenceResolver.d.ts.map