import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
export declare const SERVER_NAME = "abap-mcp";
export declare const SERVER_VERSION = "0.10.0";
export declare const SERVER_INSTRUCTIONS = "Use abap-mcp for offline analysis of ABAP source text. Start general reviews with lint_abap; for ABAP Cloud or Clean Core questions use check_cloud_readiness, then plan_cloud_migration when the user wants an actionable backlog. The tools cannot read workspace files: the client must pass source text \u2014 for whole-repo sweeps prefer the bundled CLI (npx abap-mcp readiness src/) through your shell instead of passing dozens of files through tool calls. Use check_released_api for explicit SAP object release-state lookups, scaffold_rap_bo for a new managed RAP BO, scaffold_abap_unit for a failing-by-default test harness on an existing class, get_object_dependencies to sequence migration work or read impact, fix_abap to apply abaplint's deterministic auto-fixes (the mechanical first pass before any hand or model rewrite), and compare_abap to verify a rewrite. They do not connect to SAP or run ATC. Released-API observations come from a dated bundled snapshot, so the target system remains authoritative. Use the packaged prompts for guided review, mentoring, and migration workflows.";
/** Build a fully-wired MCP server instance (one per transport connection). */
export declare function buildServer(): McpServer;