1c Rest MCP vs Notion MCP Server
A side-by-side look at the 1c Rest MCP and Notion MCP Server 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 Notion MCP Server 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 Notion MCP Server when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
NOTION_TOKEN. - You want tools like
notion_read, notion_write, notion_describe.
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 | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | NOTION_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12 | 178 |
| Directory activity | 1 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 34 | 3 |
| Full listing | View 1c Rest MCP | View Notion MCP Server |
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
Notion MCP Server tools 3
notion_readRun one Notion read operation by name. Nothing is modified. Call: { operation, payload } — payload carries that operation's fields. Common: search_pages { query }, get_page { page_id }, get_page_markdown { page_id }, query_database { database_id, where? }, get_block_children { block_id }. Responses are slimmed; pass verbose:true in payload for the raw Notion object. Every id field (page_id, block_id, database_id, view_id, …) also accepts a Notion URL, as copied from Share → Copy link. A block link's #fragment is used for block_id fields and a database link's ?v= for view_id fields. If the payload is malformed, the error response includes the schema + a working example so you can correct and retry in one round-trip. Call notion_describe(operation) ahead of time only for complex shapes (query_database filters).notion_writeRun one Notion write operation by name. Archive, trash and delete operations remove content — confirm with the user before running them. Two ways to call: • Single: { operation: "set_page_title", payload: { page_id, title } } • Batch: { operation: "set_page_title", payload: { items: [{page_id, title}, ...], atomic?: false, idempotency_key?: "...", concurrency?: 3 } } create_page, append_blocks, update_block and update_page_markdown also take a markdown string. Responses are slimmed; pass verbose:true inside payload (single) or per item (batch) for the raw Notion object. Every id field (page_id, block_id, database_id, view_id, …) also accepts a Notion URL, as copied from Share → Copy link. If the payload is malformed, the error response includes the schema + a working example so you can correct and retry in one round-trip. Call notion_describe(operation) ahead of time only for complex shapes (block trees, database property definitions, batch_mixed_blocks).notion_describeReturn the JSON Schema and a working example for one operation, plus which tool runs it (notion_read or notion_write). Use this BEFORE calling the operation when the payload shape is non-trivial (query filters, structured block trees, database property definitions). For simple ops, just call it — errors carry the schema.
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"
]
}
}
}
Notion MCP Server
{
"mcpServers": {
"awkoy-notion-mcp-server": {
"command": "npx",
"args": [
"-y",
"notion-mcp-server"
],
"env": {
"NOTION_TOKEN": "YOUR_NOTION_TOKEN_HERE"
}
}
}
}
Frequently asked questions
1c Rest MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. Notion MCP Server belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick 1c Rest MCP for other tools and integrations work and Notion MCP Server 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. Notion MCP Server is listed as free. Auth: api key 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 awkoy-notion-mcp-server 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. Notion MCP Server has 71/100 (Great) with 7 views, 0 installs and 178 GitHub stars.