http1c — это фреймворк для построения серверов протокола Model Context Protocol (MCP) от 1C:Enterprise. Он предоставляет нативный компонент (DLL), который обрабатывает транспортный уровень MCP и базовый процессор данных 1C, который демонстрирует, как реализовать инструменты, ресурсы и подсказки.

Используйте его в качестве шаблона для раскрытия любой бизнес-логики 1С — каталогов, документов, отчетов, вычислений — для приложений ИИ, таких как VS Code Copilot, Claude Desktop и других MCP-совместимых клиентов.

Основная концепция

Проект намеренно разделен на два слоя с различными обязанностями.

Родные обязанности

DLL является двигателем MCP. Он обрабатывает протокольные и транспортные детали, которые не должны быть реализованы в бизнес-коде 1С:

Транспорт HTTP/SSE Жизненный цикл JSON-RPC/Response Управление сессиями MCP

• аутентификация, проверка происхождения и ограничение скорости
• пагинация, уведомления и потоковая передача прогресса Преобразование 1С ответов в действительные MCP ответы

Обязанности 1С

1С владеет бизнес-логикой. Разработчик 1С должен работать на уровне инструментов, ресурсов и подсказок, а не на уровне внутренних компонентов MCP:

• описание инструмента/ресурса/операции в BSL

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