mcp-1c
Related Servers
Alternatives to mcp-1c
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides a RAG-based search system for 1C:Enterprise platform documentation using hybrid BM25 and semantic search across multiple versions. It enables developers to retrieve API signatures, methods, and usage examples directly within IDEs or through a REST API.22MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to search and retrieve 1C:Enterprise 8.3 syntax documentation, including quick references, detailed syntax info, and object members, through MCP tools backed by an Elasticsearch index.-
- AlicenseNot gradedqualityAmaintenanceMCP server for 1C:Enterprise that provides precise syntax reference cards (call signatures, parameters, return types, examples) by element name and lists object members. It helps AI agents answer 1C development questions using the official Russian help book.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with 1C:Enterprise databases through natural language, providing metadata retrieval, configuration analysis, and code generation.9-
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to explore and search a 1C:Enterprise configuration codebase, including metadata objects, module procedures, call graphs, and semantic similarity search.MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI assistants in Cursor with local access to 1C platform documentation and XML configuration exports, enabling metadata lookup, BSL code search, and platform help queries without manual file copying.MIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource-action pair: configurations vs extensions, configuration objects vs procedures vs platform syntax, and search vs get within the same domain. The descriptions explicitly cross-reference when to call what (e.g., get_object after search_objects, get_syntax from search_syntax results), leaving no realistic ambiguity between tools.
All 11 tools follow a consistent verb_noun snake_case pattern: list_*, search_*, get_*, compare_*. The verb reliably indicates the operation type (discover, find, retrieve, diff) and the noun the resource, making the API structure fully predictable and discoverable.
11 tools is well within the ideal 3-15 range for a 1C analysis server. Each tool earns its place: discovery, object search, code search, detail retrieval, relationship tracing, syntax reference, and comparison — no redundant or decorative tools.
The surface covers a coherent read-only analysis lifecle: discover configs and extensions, search and inspect objects and code, trace callers, look up platform syntax, and compare configs. Minor gaps exist — compare_configurations only compares attribute names (not types or tabular sections), and object discovery requires search rather than enumeration — but both are explicitly disclosed and workaroundable with get_object and targeted queries.