대한민국 교육 시설 식단 정보 조회 서버

본 MCP(Model Context Protocol) 서버는 교육부의 NEIS 공개 API를 활용하여 전국 단위의 학교별 급식 정보를 획득할 수 있도록 설계되었습니다.

핵심 기능

기관명 기반의 교육 시설 검색 기능
특정 일자의 식단 정보 추출
해당 주간의 전체 식단표 조회
구어체(자연어) 질의 응답 지원 (예: "하나고등학교 어제의 식사 내용")

구축 및 구동 절차

필요한 모듈 설치: bash npm install
환경 설정 변수 구성: 프로젝트 루트에 .env 파일을 작성하고 다음 정보를 기입하십시오: bash NEIS_API_KEY=your_api_key_here PORT=3000 TRANSPORT=ws
개발 환경 실행: bash npm run dev
운영 환경 배포 실행: bash npm run build npm start

인터페이스 활용 예시

typescript // 당일 식사 내역 요청 { "question": "하나고등학교 금일 식단" }

// 현재 주의 식사 계획 요청 { "question": "하나고등학교 이번 주 메뉴" }

환경 변수 항목

NEIS_API_KEY: NEIS 공개 API 접근 인증 키 (필수값)
PORT: 서버가 수신할 네트워크 포트 번호 (기본값: 3000)
TRANSPORT: 통신 매체 지정 (선택지: ws 또는 stdio)

배포 라이선스

ISC

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea