1c Rest MCP vs Time

A side-by-side look at the 1c Rest MCP and Time 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 declaredTime logoTimeOther Tools and Integrations · Local subprocess (stdio)Time and timezone conversion capabilities.83ExcellentAuth: no auth required

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

Time logoChoose Time 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 want tools like get_current_time, convert_time.
Explore Time

Feature & specification comparison

Rows where the two servers differ are marked.

Spec1c Rest MCP logo1c Rest MCPTime logoTime
CategoryOther Tools and IntegrationsOther Tools and Integrations
Quality signal61/100 · Good83/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars1291,526
Directory activity 1 views 0 installs 0 upvotes 5 views 0 installs 0 upvotes
Tools342

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

Time tools 2

  • get_current_timeGet current time in a specific timezone
  • convert_timeConvert time between timezones

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"
      ]
    }
  }
}

Time

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

Frequently asked questions

1c Rest MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. Time belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick 1c Rest MCP for other tools and integrations work and Time 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. Time 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 time 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. Time has 83/100 (Excellent) with 5 views, 0 installs and 91,526 GitHub stars.