1c Rest MCP vs MCP Cli

A side-by-side look at the 1c Rest MCP and MCP Cli MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

1c Rest MCP logo1c Rest MCPOther Tools and Integrations · Local subprocess (stdio)MCP server for 1C REST API -- catalogs, documents. Basic Auth, configurable base URL.61GoodAuth: not declaredMCP Cli logoMCP CliOther Tools and Integrations · Local subprocess (stdio)Yet another CLI tool for testing MCP servers33EmergingAuth: no auth required

Verdict: choose 1c Rest MCP for other tools and integrations work as a local process; choose MCP Cli 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?

1c Rest MCP logoChoose 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.
Explore 1c Rest MCP

MCP Cli logoChoose MCP Cli 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.
Explore MCP Cli

Feature & specification comparison

Rows where the two servers differ are marked.

Spec1c Rest MCP logo1c Rest MCPMCP Cli logoMCP Cli
CategoryOther Tools and IntegrationsOther Tools and Integrations
Quality signal61/100 · Good33/100 · Emerging
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars122,023
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools34Not listed

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

MCP Cli tools

No tool names declared yet. Check the project README from the listing page.

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "1c-rest-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/aprovodka"
      ]
    }
  }
}

MCP Cli

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chrishayuk-mcp-cli": {
      "command": "uvx",
      "args": [
        "mcp-server-sqlite"
      ]
    }
  }
}

Frequently asked questions

1c Rest MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. MCP Cli belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick 1c Rest MCP for other tools and integrations work and MCP Cli 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. MCP Cli 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 chrishayuk-mcp-cli 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. MCP Cli has 33/100 (Emerging) with 4 views, 0 installs and 2,023 GitHub stars.