1c Rest MCP vs Memory
A side-by-side look at the 1c Rest MCP and Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 1c Rest MCP for other tools and integrations work as a local process; choose Memory for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 1c Rest MCP when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_config_preset, list_entities, get_document_by_number.
Choose Memory when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MEMORY_FILE_PATH. - You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 61/100 · Good | 89/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | MEMORY_FILE_PATH |
| Verified owner | Community listing | Verified |
| GitHub stars | 12 | 91,540 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 34 | 9 |
| Full listing | View 1c Rest MCP | View Memory |
Tools & capabilities
1c Rest MCP tools 34
get_config_presetКурированная схема типовой конфигурации 1С (БП 3.0, УТ 11, ЗУП 3.1, ERP 2): ключевые OData-сущности с русскими описаниями, готовые примеры запросов и частые ловушки. Локальные данные — запроса к базе не делает. Вызывать ПЕРЕД list_entities, чтобы знать, что искать; без config возвращает список пресетов.list_entitiesСписок всех доступных сущностей 1С в OData: справочники (Catalog_*), документы (Document_*), все четыре вида регистров (Accumulation/Information/Accounting/CalculationRegister_*), планы видов характеристик и счетов (ChartOf*), константы (Constant_*), журналы документов (DocumentJournal_*), отчёты (Report_*). Вызывать первым при работе с незнакомой базой.get_document_by_numberПоиск документа 1С по номеру. Обёртка над OData $filter. Пример: найти реализацию ТД-00123 от 2025-03-01.get_metadataВозвращает исходный документ $metadata базы 1С (EDMX/XML) с описанием всех сущностей, полей и типов. Нужен для точной схемы; если требуется только список полей одной сущности, дешевле describe_entity.describe_entityСписок полей сущности 1С по одной образцовой записи ($top=1). Дешевле полного $metadata, когда нужны только имена полей одной сущности.get_catalogsЧтение данных справочников 1С через OData 3.0. Поддерживает $filter, $select, $orderby, $top, $skip.create_catalog_itemСоздание нового элемента справочника через OData POST (например, добавить Контрагента или позицию Номенклатуры).update_catalog_itemИзменение существующего элемента справочника через OData PATCH (по Ref_Key, GUID).get_documentsЧтение документов 1С через OData 3.0. Отбор по дате, виду документа или произвольным полям.create_documentСоздание нового документа 1С через OData POST.update_documentИзменение существующего документа 1С через OData PATCH (по Ref_Key, GUID).post_documentПроведение документа 1С через связанное действие OData Post(). Для оперативного проведения указать operational=true.- +22 more on the listing page
Memory tools 9
create_entitiesCreate multiple new entities in the knowledge graph. An entity whose name already exists, or repeats an earlier entity in the same call, is skipped and its observations are not added; the result lists the skipped names in `skipped`. Use add_observations to add observations to an existing entity.create_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
1c Rest MCP
{
"mcpServers": {
"1c-rest-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/aprovodka"
]
}
}
}
Memory
{
"mcpServers": {
"memory": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
],
"env": {
"MEMORY_FILE_PATH": "YOUR_MEMORY_FILE_PATH_HERE"
}
}
}
}
Frequently asked questions
1c Rest MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. Memory belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick 1c Rest MCP for other tools and integrations work and Memory for other tools and integrations.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
1c Rest MCP has no declared pricing — check the project's own site. Memory is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add 1c-rest-mcp and memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, 1c Rest MCP has a quality signal of 61/100 (Good) with 1 views, 0 installs and 12 GitHub stars. Memory has 89/100 (Excellent) with 9 views, 0 installs and 91,540 GitHub stars.