"Search for information related to '1c'" matching MCP servers:

Provides 1C configuration metadata, platform syntax, and query language reference for BSL coding agents. Resolves natural language terms to exact object names, returning structures, relationships, and version-aware method details.

Integrates IDEs with the 1C:Напарник API, providing code analysis tools and documentation search for 1C.

Enables agents to run local semantic, lexical, and hybrid (RRF) retrieval over 1C:Enterprise source code (.bsl) and configuration metadata reports, exposing code search, metadata search, and a unified vector/hybrid/rerank pipeline through stdio tools. It also lets users measure and compare retrieval quality per query with Hit@k, Recall@k, MRR, and nDCG@10 metrics.

MCP server for semantic search of 1C (BSL) code templates with 2262+ community templates, CRUD web interface, and ChromaDB + embeddings for meaning-based search.

Enables AI agents to drive the 1C:Enterprise test client directly, opening forms, reading and modifying data, working with tables, and recording or replaying action scenarios. Connects to local or remote test clients over their network protocol without a testing manager.

Lightweight MCP server for 1C.ai integration, enabling queries, code analysis, and documentation search via natural language.

Enables AI agents to inspect, create, and edit 1C metadata and managed forms in a configurator XML dump without manual XML editing, using metadata_check for dry-run validation and metadata_apply for writes. It enforces platform dump rules, preserves formatting, and supports operations such as object creation, property changes, renaming, role generation, and form amendments.

MCP server for generating, validating, converting, and searching managed 1C:Enterprise forms in three formats: Configurator, Managed, and EDT.

Enables AI agents to interact with 1C: Enterprise development environment, including running tests, managing launch profiles, building configurations, and performing database operations through the 1C: Platform Tools extension.

Enables 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.

Provides 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.

Enables AI agents to search and read 1C:ITS portal subscription materials, such as development standards, platform documentation, and configuration guides, returning content as Markdown with source links.

A local read-only AI workbench for navigating, auditing, and analyzing 1C:Enterprise 8.3 configurations via MCP-compatible clients.

MCP 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.

MCP сервер с встроенным AI агентом для поиска по графу метаданных и кода конфигураций 1С

Enables 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.

Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.

Enables MCP clients to turn Make blueprints and Zapier exports into n8n workflow files, with a per-step report of what converted, what to review, and what must be finished by hand. Also lists zaps, explains how individual steps are handled, checks workflow files for broken links or placeholders, and can upload the result to an n8n instance as an inactive workflow.

MCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.

Routes one brief to the right image model across 60+ (gpt-image-1.5, Ideogram 3, Recraft V4, Flux), validates the output, and fans out to iOS/Android/PWA/favicon/visionOS/Flutter bundles. Works without an API key via Pollinations, HF Inference, Stable Horde, or host-LLM inline SVG.

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

A Model Context Protocol server that converts Markdown content to HTML format.

Enables an MCP-compatible AI client to author Blender Python, run Blender, import the resulting asset into Unity with materials and a prefab, place it in the active scene, verify the import, and revise the same asset using stable IDs.

Enables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.

Generates standalone, human-readable MCP servers from RAML 1.0 or OpenAPI 3.x specs, exposing one tool per resource and method that makes real HTTP calls. It understands Mule/Anypoint auth patterns such as Client ID enforcement and OAuth2, wiring the expected credentials from environment variables at call time.

Turns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.

Transforms Figma design data into a compact, LLM-friendly format for code generation, reducing size by 99.5% while preserving UI-critical information.

Deterministic Markdown-to-Word (.docx) publishing compiler with native OMML equations, three-line tables, CSL citations, and quality gates for AI agents.

Enables existing Express routers to be exposed as MCP tools, dispatching tool calls through the Express middleware stack in-process without a network hop.