@theyahia/1c-rest-mcp
OfficialRelated Servers
Alternatives to @theyahia/1c-rest-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityAmaintenanceMCP server for 1C:Enterprise ERP with 35 tools: metadata inspection, document CRUD, register queries, and BSP integration. First MCP server for Russian ERP systems (300,000+ organizations). JSON-RPC 2.0 compliant BSL implementation.5133MIT- AlicenseNot gradedqualityAmaintenanceMCP сервер с встроенным AI агентом для поиска по графу метаданных и кода конфигураций 1С97AGPL 3.0
- AlicenseAqualityCmaintenanceMCP server for full lifecycle of 1C binary files (CF/CFE/EPF/ERF) without EDT import: unpack to a temporary directory, read and edit code/forms/help, search, diff, repack, and cleanup. Enables code analysis, patching, and bytecode decompilation of protected modules via natural language.205MIT
- AlicenseNot gradedqualityBmaintenanceIntegrates AI agents with 1C:Enterprise databases via MCP and REST API, supporting a built-in HTTP server (no Python required) or a Python proxy mode.264GPL 3.0
- FlicenseNot gradedqualityDmaintenanceActs as a bridge between AI agents (Claude, Cursor) and 1C:Enterprise databases, enabling metadata retrieval, configuration analysis, and code generation through natural language using the MCP protocol.-
- AlicenseNot gradedqualityBmaintenanceMCP server that provides read-only access to 1C:Enterprise configuration metadata extracted into SQLite, enabling LLMs to inspect objects, modules, and validate 1C queries.MIT
TDQS
Scored across 9 tools
Most tools have distinct purposes, but get_documents and odata_query overlap somewhat since odata_query can retrieve documents as well. However, the specialized tools (get_document_by_number, get_catalogs, etc.) maintain clear boundaries.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_document, get_catalogs, update_document). No deviations or mixed conventions.
9 tools is well-scoped for a 1C REST server, covering documents, catalogs, registers, reports, and a generic query tool. Not excessive or insufficient.
Document lifecycle has create, read (multiple), update but lacks delete. No update or delete for catalogs/registers. Minor gaps like missing delete operations, but core read/write coverage is present.