1c Rest MCP vs Server Everything
A side-by-side look at the 1c Rest MCP and Server Everything 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 Server Everything 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 Server Everything 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
echo, get-annotated-message, get-env.
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 | 73/100 · Great |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12 | 91,525 |
| Directory activity | 1 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 34 | 16 |
| Full listing | View 1c Rest MCP | View Server Everything |
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
Server Everything tools 16
echoEchoes back the input stringget-annotated-messageDemonstrates how annotations can be used to provide metadata about content.get-envReturns all environment variables, helpful for debugging MCP server configurationget-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.get-resource-linksReturns up to ten resource links that reference different types of resourcesget-resource-referenceReturns a resource reference that can be used by MCP clientsget-structured-contentReturns structured content along with an output schema for client data validationget-sumReturns the sum of two numbersget-tiny-imageReturns a tiny MCP logo image.gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.- +4 more on 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": {
"1c-rest-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/aprovodka"
]
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
1c Rest MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick 1c Rest MCP for other tools and integrations work and Server Everything 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. Server Everything 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 modelcontextprotocol-server-everything 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. Server Everything has 73/100 (Great) with 9 views, 0 installs and 91,525 GitHub stars.