/**
 * Interpreter detection for MCP server commands.
 *
 * When an MCP server's `command` field is a well-known interpreter (python,
 * node), we treat it as an external CLI the plugin depends on — it must be
 * present on the target runtime. This gives MCP-rich plugins (especially
 * python-based ones) a meaningful `CAPABILITY_EXTERNAL_CLI` signal.
 *
 * Unknown/bespoke commands (e.g. `./scripts/my-server.sh`) are intentionally
 * left alone — we don't speculate about what they require.
 */
/**
 * Normalize an MCP server command to a canonical external-CLI binary name,
 * or `undefined` if the command is not a recognized interpreter.
 *
 * Handles absolute paths (`/usr/bin/python3`, `/opt/homebrew/bin/node`),
 * versioned suffixes (`python3.11`), and plain names (`python3`, `node`).
 */
export declare function detectInterpreter(command: string): string | undefined;
/**
 * Extract the command string from an `MCP_SERVER_COMMAND` evidence record's
 * matchText. The mcp-config-scanner emits matchText of the form
 * `MCP server "<name>" command: <command>`.
 *
 * Returns `undefined` if the pattern is unrecognized (e.g. evidence from a
 * different scanner shape).
 */
export declare function extractMcpCommandFromMatchText(matchText: string): string | undefined;
//# sourceMappingURL=interpreter-detection.d.ts.map