MCP server intelligence profile

@theyahia/1c-rest-mcp Server

MCP-сервер для REST API 1С:Предприятие через OData 3.0 -- справочники, документы, регистры, отчёты

Local OnlyOfficial distributiontheYahia
Verified cleanNpm · 3.2.0

Our scanner tested version 3.2.0 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.

1Distribution channel
32Independently observed tools
0Linked remote endpoints
AvailableVersion intelligence

Install and connect

Installation and connection instructions are shown only when supported by retained package, repository, or endpoint evidence.

Install @theyahia/1c-rest-mcp from npm

Version 3.2.0 declares 1 executable entrypoint.

npm install --save-exact @theyahia/1c-rest-mcp@3.2.0
npx -y -p @theyahia/1c-rest-mcp@3.2.0 @theyahia/1c-rest-mcp
MCP client configuration example
{
  "mcpServers": {
    "@theyahia/1c-rest-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@theyahia/1c-rest-mcp@3.2.0",
        "@theyahia/1c-rest-mcp"
      ]
    }
  }
}

Identity

Canonical slugtheyahia-1c-rest-mcp-94c2e114DeploymentLocal Only
Canonical packagenpm:@theyahia/1c-rest-mcpRepositorytheYahia/aprovodka
First published—Latest release—
Last security verificationAug 20, 2026Classification confidence90%
PublicationPublishedOfficial distributionYes

Distributions

ChannelIdentifierCurrent versionVersionsSource
npm@theyahia/1c-rest-mcp3.2.01Repository

Current release

PackageVersionPublished / observedInventorySecurity scan
npm@theyahia/1c-rest-mcp3.2.0CurrentSep 5, 202632 toolsSucceeded · 0 resources · 3 promptsVerified clean
Enterprise protection

Continuously monitor this MCP for security risk

Independently scan the exact version your agents use, receive alerts when its risk changes, and investigate every finding with retained version evidence.

  • Independent exact-version security scans
  • Continuous release and vulnerability monitoring
  • Risk-change alerts with capability context
  • Historical evidence and API exports
Custom pricingContact salesTailored to your organization, integrations, data needs, and support requirements.

Current version evidence

Provenanceartifact_hash_verifiedSignature—
MCP SDK@modelcontextprotocol/sdk Artifact SHA-25637c63f7281f5bf74dceeaf5387a3f19b014588b9cc9b37de152c14d0ed9aa7c8
Scannermcp-proof-engine 0.1.0Scan completedAug 20, 2026
Security rating30 / 100Methodologyversion-rating-1.0
Executable entrypoints
[
  "@theyahia/1c-rest-mcp"
]
Rating reasons
[
  "security_policy_not_observed"
]
0Proven
3052Clean
0Inconclusive
0Flaky
0Errors

Current protocol inventory

2025-06-18Negotiated protocol
1c-rest-mcpServer-reported name
2Capability groups
Aug 17, 2026Observed

Tools 32

ToolCategoryAnnotationsRisk
batch_create_documentsCreate N 1C documents in parallel (1..100 per call). 1C does NOT support OData $batch — this is client-side parallel batching with concurrency cap and per-item success/failure reporting.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Type of all documents (e.g. Document_РеализацияТоваровУслуг). Same type for the whole batch."
    },
    "documents": {
      "minItems": 1,
      "maxItems": 100,
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      },
      "description": "Array of document payloads (1..100). Each item is the same shape as `create_document.data`."
    },
    "concurrency": {
      "default": 5,
      "description": "Max parallel HTTP requests to 1C. Default 5 — safe for most 1C deployments.",
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    }
  },
  "required": [
    "document_type",
    "documents"
  ]
}
——
batch_queryRun N 1C OData queries in parallel (1..50). Each query reported individually. No server-side join (1C does not support $batch) — combine results client-side.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "queries": {
      "minItems": 1,
      "maxItems": 50,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "entity": {
            "type": "string",
            "description": "OData entity (e.g. Catalog_Номенклатура)."
          },
          "filter": {
            "description": "$filter clause.",
            "type": "string"
          },
          "select": {
            "description": "$select clause.",
            "type": "string"
          },
          "expand": {
            "description": "$expand clause.",
            "type": "string"
          },
          "top": {
            "default": 100,
            "type": "integer",
            "minimum": 1,
            "maximum": 5000
          },
          "skip": {
            "default": 0,
            "type": "integer",
            "minimum": 0,
            "maximum": 9007199254740991
          },
          "orderby": {
            "type": "string"
          }
        },
        "required": [
          "entity"
        ]
      },
      "description": "Array of OData GET specs (1..50). Each runs as a separate HTTP request."
    },
    "concurrency": {
      "default": 5,
      "description": "Max parallel HTTP requests. Default 5.",
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    }
  },
  "required": [
    "queries"
  ]
}
——
batch_update_catalog_itemsUpdate N 1C catalog items in parallel (1..100). Each item updated via OData PATCH on its Ref_Key. Per-item success/failure reported; partial failures do not abort the batch.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "catalog_name": {
      "type": "string",
      "description": "Catalog entity name (e.g. Catalog_Номенклатура)."
    },
    "updates": {
      "minItems": 1,
      "maxItems": 100,
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "ref_key": {
            "type": "string",
            "description": "Ref_Key (GUID) of the item to update."
          },
          "data": {
            "type": "object",
            "propertyNames": {
              "type": "string"
            },
            "additionalProperties": {},
            "description": "Fields to update — same shape as `update_document.data`."
          }
        },
        "required": [
          "ref_key",
          "data"
        ]
      },
      "description": "Array of (ref_key, data) tuples (1..100)."
    },
    "concurrency": {
      "default": 5,
      "description": "Max parallel HTTP requests. Default 5.",
      "type": "integer",
      "minimum": 1,
      "maximum": 20
    }
  },
  "required": [
    "catalog_name",
    "updates"
  ]
}
——
count_entitiesCount records of an entity ($inlinecount, $top=0) with an optional filter.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Сущность для подсчёта (например, Document_РеализацияТоваровУслуг)"
    },
    "filter": {
      "description": "OData $filter для условия подсчёта",
      "type": "string"
    }
  },
  "required": [
    "entity"
  ]
}
——
create_catalog_itemCreate a new catalog item via OData POST (e.g. add a Контрагент or Номенклатура).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "catalog_name": {
      "type": "string",
      "description": "Имя справочника (например, Catalog_Номенклатура)"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "Поля нового элемента в формате JSON (например, {\"Description\":\"Молоко\"})"
    }
  },
  "required": [
    "catalog_name",
    "data"
  ]
}
——
create_documentCreate a new 1C document via OData POST.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа (например, Document_РеализацияТоваровУслуг)"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "Данные документа в формате JSON"
    }
  },
  "required": [
    "document_type",
    "data"
  ]
}
——
delete_documentPhysically delete a 1C document via OData DELETE (by Ref_Key). Prefer set_deletion_mark for a recoverable soft delete.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key документа (GUID)"
    }
  },
  "required": [
    "document_type",
    "ref_key"
  ]
}
——
describe_entityList the fields of a 1C entity by inspecting one sample record ($top=1). Cheaper than reading full $metadata when you only need field names of one entity.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Имя сущности (например, Catalog_Номенклатура, Document_РеализацияТоваровУслуг)"
    }
  },
  "required": [
    "entity"
  ]
}
——
find_by_descriptionFuzzy-find items by a substring of their Description (OData substringof).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Сущность для поиска (например, Catalog_Контрагенты)"
    },
    "query": {
      "type": "string",
      "description": "Подстрока для поиска в поле Description"
    },
    "top": {
      "default": 20,
      "description": "Сколько записей вернуть",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    }
  },
  "required": [
    "entity",
    "query"
  ]
}
——
get_accounting_registerRead accounting-register records (AccountingRegister_*, e.g. Хозрасчетный — проводки) via OData.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "register_name": {
      "default": "Хозрасчетный",
      "description": "Имя регистра бухгалтерии (по умолчанию Хозрасчетный — основной план счетов)",
      "type": "string"
    },
    "filter": {
      "description": "OData $filter (например, Period ge datetime'2024-01-01T00:00:00')",
      "type": "string"
    },
    "select": {
      "description": "OData $select",
      "type": "string"
    },
    "top": {
      "default": 100,
      "description": "$top",
      "type": "integer",
      "minimum": 1,
      "maximum": 5000
    },
    "skip": {
      "default": 0,
      "description": "$skip",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "orderby": {
      "description": "OData $orderby (например, Period desc)",
      "type": "string"
    }
  }
}
——
get_accumulation_balanceGet accumulation-register balances (остатки) via the 1C OData virtual method Balance(Period=…,Condition=…). Omit period for current balances.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "register_name": {
      "type": "string",
      "description": "Имя регистра накопления (например, ОстаткиТоваровНаСкладах)"
    },
    "period": {
      "description": "Дата среза остатков YYYY-MM-DDTHH:MM:SS (Period). Без указания — текущие остатки.",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}$"
    },
    "condition": {
      "description": "OData-условие отбора измерений (Condition), например \"Склад_Key eq guid'…'\"",
      "type": "string"
    }
  },
  "required": [
    "register_name"
  ]
}
——
get_by_keyFetch a single 1C record by its Ref_Key (GUID).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Сущность (например, Catalog_Номенклатура)"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key (GUID)"
    },
    "select": {
      "description": "OData $select",
      "type": "string"
    }
  },
  "required": [
    "entity",
    "ref_key"
  ]
}
——
get_catalogsRead 1C catalog data via OData 3.0. Supports $filter, $select, $orderby, $top, $skip.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "catalog_name": {
      "type": "string",
      "description": "Имя справочника (например, Catalog_Номенклатура)"
    },
    "filter": {
      "description": "OData $filter (например, Description eq 'Молоко')",
      "type": "string"
    },
    "select": {
      "description": "OData $select (например, Ref_Key,Description)",
      "type": "string"
    },
    "top": {
      "default": 100,
      "description": "Количество записей ($top)",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "skip": {
      "default": 0,
      "description": "Пропустить записей ($skip)",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "orderby": {
      "description": "OData $orderby (например, Description asc)",
      "type": "string"
    }
  },
  "required": [
    "catalog_name"
  ]
}
——
get_constantRead a 1C constant value (Constant_*).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "constant_name": {
      "type": "string",
      "description": "Имя константы (например, Constant_ОсновнаяВалюта или ОсновнаяВалюта)"
    }
  },
  "required": [
    "constant_name"
  ]
}
——
get_document_by_numberFind a 1C document by its number. Convenience wrapper over OData $filter. Example: locate invoice ТД-00123 dated 2025-03-01.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа (например, Document_РеализацияТоваровУслуг)"
    },
    "number": {
      "type": "string",
      "description": "Номер документа"
    },
    "date": {
      "description": "Дата создания документа в формате YYYY-MM-DD (необязательно, сужает поиск)",
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "select": {
      "description": "Поля для выборки через OData $select (например, Ref_Key,Number,Date)",
      "type": "string"
    }
  },
  "required": [
    "document_type",
    "number"
  ]
}
——
get_document_linesRead a document's tabular section (строки / табличная часть, e.g. Товары) by Ref_Key via OData $expand. The section name is configuration-specific — discover it with get_metadata / describe_entity.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа (например, Document_РеализацияТоваровУслуг)"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key документа (GUID)"
    },
    "tabular_section": {
      "type": "string",
      "description": "Имя табличной части (например, Товары, Услуги). Имя конфиг-зависимо — проверьте через get_metadata / describe_entity, если не уверены."
    }
  },
  "required": [
    "document_type",
    "ref_key",
    "tabular_section"
  ]
}
——
get_documentsRead 1C documents via OData 3.0. Filter by date, type, or arbitrary fields.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа (например, Document_РеализацияТоваровУслуг)"
    },
    "filter": {
      "description": "OData $filter (например, Date ge datetime'2024-01-01T00:00:00')",
      "type": "string"
    },
    "select": {
      "description": "OData $select",
      "type": "string"
    },
    "top": {
      "default": 100,
      "description": "Количество записей ($top)",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "skip": {
      "default": 0,
      "description": "Пропустить записей ($skip)",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "orderby": {
      "description": "OData $orderby",
      "type": "string"
    }
  },
  "required": [
    "document_type"
  ]
}
——
get_metadataReturn the raw 1C OData $metadata document (EDMX/XML) describing every entity, field and type in the database. Use for exact schema; for a quick field list prefer describe_entity.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {}
}
——
get_recent_documentsGet the most recent documents of a type, ordered by Date desc (optionally posted only).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа (например, Document_РеализацияТоваровУслуг)"
    },
    "top": {
      "default": 10,
      "description": "Сколько последних документов",
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    },
    "posted_only": {
      "default": false,
      "description": "Только проведённые (Posted eq true)",
      "type": "boolean"
    }
  },
  "required": [
    "document_type"
  ]
}
——
get_registerRead 1C information or accumulation register data via OData 3.0.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "register_type": {
      "type": "string",
      "enum": [
        "InformationRegister",
        "AccumulationRegister"
      ],
      "description": "Тип регистра"
    },
    "register_name": {
      "type": "string",
      "description": "Имя регистра (например, ЦеныНоменклатуры)"
    },
    "filter": {
      "description": "OData $filter",
      "type": "string"
    },
    "select": {
      "description": "OData $select",
      "type": "string"
    },
    "top": {
      "default": 100,
      "description": "$top",
      "type": "integer",
      "minimum": 1,
      "maximum": 5000
    },
    "skip": {
      "default": 0,
      "description": "$skip",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "orderby": {
      "description": "OData $orderby",
      "type": "string"
    }
  },
  "required": [
    "register_type",
    "register_name"
  ]
}
——
get_reportGet a 1C report via an arbitrary HTTP service URL (/hs/...).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "report_url": {
      "type": "string",
      "description": "Полный относительный путь к отчёту (например, /hs/reports/balance?date=2024-12-31)"
    }
  },
  "required": [
    "report_url"
  ]
}
——
list_entitiesList all available 1C OData entities: catalogs (Catalog_*), documents (Document_*), registers (AccumulationRegister_*, InformationRegister_*), reports (Report_*). Use this first when working with an unfamiliar database.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "type": {
      "default": "all",
      "description": "Фильтр по типу: all — все сущности, catalogs — справочники (Catalog_*), documents — документы (Document_*), registers — регистры (AccumulationRegister_*, InformationRegister_*), reports — отчёты (Report_*)",
      "type": "string",
      "enum": [
        "all",
        "catalogs",
        "documents",
        "registers",
        "reports"
      ]
    },
    "search": {
      "description": "Подстрока для поиска в имени сущности (например, 'Номенклатура')",
      "type": "string"
    }
  }
}
——
list_subscriptionsDocuments that 1C does NOT support webhook subscriptions. Returns empty list + workaround hints (use poll_changes_since instead). Prevents LLMs from hallucinating subscribe_to_event flows.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {}
}
——
odata_queryRun an arbitrary OData 3.0 query against any 1C entity. Supports $filter, $select, $expand, $orderby, $top, $skip, $inlinecount.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "OData-сущность (например, Catalog_Номенклатура, Document_СчётНаОплатуПокупателю)"
    },
    "filter": {
      "description": "$filter",
      "type": "string"
    },
    "select": {
      "description": "$select",
      "type": "string"
    },
    "expand": {
      "description": "$expand для связанных таблиц",
      "type": "string"
    },
    "top": {
      "default": 100,
      "description": "$top",
      "type": "integer",
      "minimum": 1,
      "maximum": 5000
    },
    "skip": {
      "default": 0,
      "description": "$skip",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "orderby": {
      "description": "$orderby",
      "type": "string"
    },
    "inlinecount": {
      "default": false,
      "description": "Добавить $inlinecount=allpages",
      "type": "boolean"
    }
  },
  "required": [
    "entity"
  ]
}
——
poll_changes_sincePoll a 1C entity for rows modified since a timestamp cursor. 1C does NOT support webhooks — use this on a schedule (every 30-300s). Returns rows + a `next_cursor` for the next poll.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "OData entity to poll (e.g. Document_РеализацияТоваровУслуг, Catalog_Номенклатура)."
    },
    "since": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}$",
      "description": "ISO timestamp cursor (YYYY-MM-DDTHH:mm:ss). Rows with `Date` >= since are returned. On first poll, pass a recent timestamp. Subsequent polls should use `next_cursor` from the previous response."
    },
    "date_field": {
      "default": "Date",
      "description": "Name of the date field to filter on. Defaults to `Date` (works for most documents). For catalogs/registers without `Date`, override with e.g. `ModificationDate` or similar. Note: 1C metadata is per-config — verify field exists via `list_entities` / a sample query.",
      "type": "string"
    },
    "top": {
      "default": 100,
      "description": "Max rows per poll. Default 100. Use $top on follow-up polls for paging.",
      "type": "integer",
      "minimum": 1,
      "maximum": 1000
    },
    "select": {
      "description": "Optional $select to limit returned fields.",
      "type": "string"
    }
  },
  "required": [
    "entity",
    "since"
  ]
}
——
post_documentPost (провести) a 1C document via the OData bound action Post(). Set operational=true for оперативное проведение.
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа (например, Document_РеализацияТоваровУслуг)"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key документа (GUID)"
    },
    "operational": {
      "default": false,
      "description": "Оперативное проведение (PostingModeOperational). По умолчанию false — неоперативное.",
      "type": "boolean"
    }
  },
  "required": [
    "document_type",
    "ref_key"
  ]
}
——
set_constantWrite a 1C constant value via OData PATCH (Value field).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "constant_name": {
      "type": "string",
      "description": "Имя константы (Constant_* или короткое имя)"
    },
    "value": {
      "description": "Новое значение константы (поле Value)"
    }
  },
  "required": [
    "constant_name",
    "value"
  ]
}
——
set_deletion_markSet or clear the DeletionMark on a catalog item or document (recoverable soft delete).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "entity": {
      "type": "string",
      "description": "Сущность (Catalog_* или Document_*)"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key (GUID)"
    },
    "mark": {
      "default": true,
      "description": "true — пометить на удаление, false — снять пометку",
      "type": "boolean"
    }
  },
  "required": [
    "entity",
    "ref_key"
  ]
}
——
unpost_documentUnpost (отменить проведение) a 1C document via the OData bound action Unpost().
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key документа (GUID)"
    }
  },
  "required": [
    "document_type",
    "ref_key"
  ]
}
——
update_catalog_itemUpdate an existing catalog item via OData PATCH (by Ref_Key GUID).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "catalog_name": {
      "type": "string",
      "description": "Имя справочника"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key элемента (GUID)"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "Обновляемые поля"
    }
  },
  "required": [
    "catalog_name",
    "ref_key",
    "data"
  ]
}
——
update_documentUpdate an existing 1C document via OData PATCH (by Ref_Key GUID).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "document_type": {
      "type": "string",
      "description": "Тип документа"
    },
    "ref_key": {
      "type": "string",
      "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
      "description": "Ref_Key документа (GUID)"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "Обновляемые поля"
    }
  },
  "required": [
    "document_type",
    "ref_key",
    "data"
  ]
}
——
write_information_registerWrite a record into an independent information register (OData POST on InformationRegister_*).
Input schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "register_name": {
      "type": "string",
      "description": "Имя регистра сведений (например, ЦеныНоменклатуры)"
    },
    "data": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {},
      "description": "Запись регистра: измерения + ресурсы (например, {\"Period\":\"2024-01-01T00:00:00\",\"Номенклатура_Key\":\"...\",\"Цена\":100})"
    }
  },
  "required": [
    "register_name",
    "data"
  ]
}
——

Resources 0

  • None observed.

Resource templates 0

  • None observed.

Prompts 3

  • find-and-post-documentfind-and-post-document

    Find a 1C document and post (провести) it — with a mandatory human confirmation before the write.

  • inventory-databaseinventory-database

    Inventory an unfamiliar 1C database — discover entities, counts and key fields.

  • reconcile-balancesreconcile-balances

    Reconcile accumulation-register balances (остатки) against the underlying movements.

Remote endpoints

EndpointTransportAuthenticationHealthObserved
No verified remote endpoint is linked.

@theyahia/1c-rest-mcp Server questions

How do I install @theyahia/1c-rest-mcp Server?

Install the selected package version with: npm install --save-exact @theyahia/1c-rest-mcp@3.2.0

What tools does @theyahia/1c-rest-mcp Server provide?

@theyahia/1c-rest-mcp Server exposed 32 tools during independent protocol observation, including batch_create_documents, batch_query, batch_update_catalog_items, count_entities, create_catalog_item, create_document, delete_document, describe_entity, and others.

Is @theyahia/1c-rest-mcp Server secure?

Our scanner tested version 3.2.0 without proving a finding in the methods exercised. This is not a guarantee that every deployment is secure.

Explore related MCP server guides

Curated product and capability guides containing this catalog record.

Official vs Community MCP ServersMCP Servers With Completed Verification

Let’s talk about MCP security.

Share your details and our security team will contact you.