http1c는 1C:Enterprise에서 Model Context Protocol (MCP) 서버를 구축하기위한 프레임 워크입니다. MCP 전송 층과 참조 1C 데이터 프로세서를 처리하는 기본 구성 요소 (DLL)를 제공합니다. 도구, 리소스 및 프롬프트를 구현하는 방법을 보여줍니다.

1C 비즈니스 로직을 노출하기 위해 템플릿을 사용하여 - 카탈로그, 문서, 보고서, 계산 - VS Code Copilot, Claude Desktop 및 기타 MCP 호환 클라이언트와 같은 AI 응용 프로그램에.

핵심 개념

프로젝트는 의도적으로 다른 책임과 2개의 층으로 분할됩니다.

네이티브 부품 책임

DLL은 MCP 엔진입니다. 그것은 프로토콜을 처리하고 1C 비즈니스 코드에서 재배되지 않은 전송 세부 사항 :

• HTTP/SSE 수송
• JSON-RPC 요청 / 응답 수명주기
• MCP 세션 관리
• 인증, 원산지 검증 및 제한 비율
• pagination, 알림 및 진행성 스트리밍
• 유효한 MCP replies로 1C 응답 변환

1C 책임

1C 측은 사업 논리를 소유합니다. 1C 개발자는 MCP 내부의 수준에 관계없이 도구, 리소스 및 프롬프트의 수준에서 작업해야합니다.

• BSL에 있는 공구/출원/prompt를 설명하십시오

http1c — MCP Server Framework for 1C:Enterprise

http1c is a framework for building Model Context Protocol (MCP) servers from 1C:Enterprise. It provides a native component (DLL) that handles the MCP transport layer and a reference 1C data processor that demonstrates how to implement tools, resources, and prompts.

Use it as a template to expose any 1C business logic — catalogs, documents, reports, calculations — to AI applications like VS Code Copilot, Claude Desktop, and other MCP-compatible clients.

Core Concept

The project is intentionally split into two layers with different responsibilities.

Native component responsibilities

The DLL is the MCP engine. It handles protocol and transport details that should not be reimplemented in 1C business code:

• HTTP/SSE transport
• JSON-RPC request/response lifecycle
• MCP session management
• authentication, origin validation, and rate limiting
• pagination, notifications, and progress streaming
• converting 1C responses into valid MCP replies

1C responsibilities

The 1C side owns business logic. A 1C developer should work at the level of tools, resources, and prompts, not at the level of MCP internals:

• describe a tool/resource/prompt in BSL
• register it in the component
• handle the incoming call in 1C
• run any required client-side or server-side 1C logic
• return the result or send progress updates

Why the project is designed this way

The goal is to let a 1C developer publish almost any 1C functionality through MCP without having to understand HTTP, JSON-RPC, SSE, session handling, or MCP message formatting.

In other words:

• the component knows how to be an MCP server
• 1C knows what the tool actually does

This keeps the integration point simple. To add new functionality, a 1C developer does not need to change the native transport layer. They only add or update 1C definitions and handlers.

Mental model for a 1C developer

From the 1C side, the workflow is intentionally simple:

1. Define the MCP object in BSL.
2. Register it in the component.
3. Receive the request through ExternalEvent.
4. Execute arbitrary 1C logic.
5. Return the final result, and optionally send progress while the operation is running.

This means the project is not a fixed set of built-in utilities. It is an MCP transport and protocol layer for 1C, with the actual application behavior defined in 1C code.

Key Features

• Full MCP protocol support — tools, resources, prompts with listChanged notifications
• Streamable HTTP transport — POST /mcp for requests, GET /mcp for SSE notification stream
• Session management — Mcp-Session-Id header, UUID v4 sessions per spec
• Security — Origin validation (DNS rebinding protection), Bearer token auth, rate limiting
• Progress streaming — SSE-based progress notifications for long-running operations