live-mcp-for-1c
Related Servers
Alternatives to live-mcp-for-1c
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Cursor and Claude to query and inspect 1C:Enterprise infobase data via COM without configuration extensions or changes, using 1C query language and metadata tools.2MIT
- AlicenseAqualityBmaintenanceConnects 1C:Enterprise databases to any MCP client through the standard OData interface, enabling natural-language access to financial, accounting, inventory, and document data; read-only by default with opt-in, preview-gated write operations.75366 npmMIT
- 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.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying and interacting with 1C:Enterprise databases via COM connection without modifying the database.-
- AlicenseNot gradedqualityCmaintenanceEnables read-only querying and schema inspection of SQL Server databases from MCP clients, exposing tools to run guarded SELECT queries, list databases and tables, and describe table columns, types, defaults, and primary keys.MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for searching and analyzing 1C enterprise metadata and BSL code using a SQLite backend. Enables querying configuration structure, code routines, and performing compliance checks via natural language.-
TDQS
Scored across 6 tools
Each tool pairs a distinct verb with a distinct target: execute vs validate for 1C queries, execute vs render for DCS schemas, and ping vs get_service_info for service introspection. The main risk is confusing execute_dcs_schema with render_dcs_schema and ping_service with get_service_info, but the descriptions clearly separate their outputs (value collection vs XLSX, availability vs metadata).
All six tools follow a consistent verb_noun convention (execute_1c_query, validate_1c_query, execute_dcs_schema, render_dcs_schema, ping_service, get_service_info). The embedded domain tokens (1c, dcs) are used consistently within their families, making the pattern predictable.
Six tools is well-scoped for a read-only 1C data-access service: two query operations, two DCS operations, and two introspection tools. Every tool earns its place with no redundant surface.
Core lifecycle covers validate→execute for queries and execute→render for DCS, plus health and metadata discovery. Minor gaps remain, such as no schema/metadata browsing to discover available tables or fields before writing a query, forcing reliance on get_service_info or trial-and-error validation.