1c Rest MCP vs Mistral MCP
A side-by-side look at the 1c Rest MCP and Mistral MCP 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 Mistral MCP 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 Mistral MCP 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:
MISTRAL_API_KEY. - You want tools like
mistral_chat, codestral_fim, mistral_vision.
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 | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | MISTRAL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 12 | 15 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 34 | 8 |
| Full listing | View 1c Rest MCP | View Mistral MCP |
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
Mistral MCP tools 8
mistral_chatGenerate a chat completion using a Mistral model. When to use: - Drafting French (or any European-language) content where Mistral shines. - Codestral for code-specific generation/review. - Ministral for cheap / low-latency classification. Returns structured content with the assistant text and token usage. Does NOT stream — use mistral_chat_stream for long outputs with progress updates.codestral_fimFill-in-the-middle code completion with Codestral. Given `prompt` (code preceding the cursor) and `suffix` (code after the cursor), Codestral writes the middle. Use for editor autocomplete scenarios, code-patching agents, or structured refactors where you know the target boundaries. Default stop tokens: [] — let the model decide. Override with `stop` if needed.mistral_visionChat completion with multimodal input: text + image_url parts. Requires a vision-capable model. Accepted: - pixtral-large-latest - pixtral-12b-latest - mistral-large-latest - mistral-medium-latest - mistral-small-latest Each message's `content` is either a plain string (pure text) or an array of parts `{ type: 'text', text }` / `{ type: 'image_url', imageUrl }`. The image URL can be an https URL or a data: URI base64 payload. Returns the assistant text + token usage. For non-visual requests, prefer `mistral_chat`.mistral_ocrRun Mistral OCR on a PDF or image, returning structured markdown per page. Input `document` is one of: - { type: "document_url", documentUrl: "https://...pdf" } - { type: "image_url", imageUrl: "https://..." | "data:image/..." } - { type: "file", fileId: "<id-from-files-api>" } Options: - `pages`: array of 0-indexed page numbers or string like "0-5,7". - `tableFormat`: 'markdown' (default) or 'html'. - `extractHeader` / `extractFooter`: include page header/footer when present. - `includeImageBase64`: embed extracted image bytes as base64 in the response. - `document_annotation_format`: JSON schema for whole-document structured extraction. - `bbox_annotation_format`: JSON schema for extracted image / bbox annotations. - `confidence_scores_granularity`: 'page' or 'word'. Returns `pages[].markdown` plus optional `pages[].hyperlinks`, `header`, `footer`, `images` bounding boxes, annotations, confidence scores, and `dimensions`.voxtral_transcribeTranscribe an audio file to text using Mistral Voxtral. Accepted models: - voxtral-mini-latest - voxtral-small-latest Audio source is one of: - { type: "file_url", fileUrl: "https://..." } (public URL) - { type: "file", fileId: "<id-from-files-api>" } Options: - `language`: ISO-639-1 hint (e.g. 'fr', 'en'). Boosts accuracy when known. - `temperature`: sampling temperature. - `diarize`: return per-speaker segments (default false). - `timestampGranularities`: ['segment'] to return per-segment timestamps. - `contextBias`: list of phrases/terms that should bias the decoder. Returns plain `text`, detected `language`, optional `segments[]`, and token usage.workflow_executeStart a Mistral Workflow execution. `workflowIdentifier` is the workflow name or ID (visible in mistral://workflows). `input` is a free-form JSON object matching the workflow's input schema. Modes: - waitForResult=false (default): returns immediately with execution_id and RUNNING status. Poll workflow_status to track completion. - waitForResult=true: blocks until the workflow finishes and returns the result inline. Use timeoutSeconds (default 30) to cap the wait. Use deploymentName to target a specific deployment slot when multiple are configured.workflow_statusGet the current state and result of a workflow execution. Statuses: RUNNING | COMPLETED | FAILED | CANCELED | TERMINATED | CONTINUED_AS_NEW | TIMED_OUT | RETRYING_AFTER_ERROR Poll until status is COMPLETED (or terminal) when waitForResult was false. `result` is populated once the workflow reaches a terminal state.workflow_interactSend a signal to or run a query against a running workflow execution. action=signal: fire-and-forget event; the workflow reacts asynchronously. - `name`: signal name defined in the workflow. - `input`: optional payload matching the signal's schema. action=query: synchronous read of internal workflow state. - `name`: query handler name defined in the workflow. - `input`: optional parameters for the query. - Returns `query_name` + `result` inline. action=update: synchronous request to modify workflow state mid-execution. - `name`: update handler name defined in the workflow. - `input`: optional payload for the update. - Returns `update_name` + `result` inline.
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"
]
}
}
}
Mistral MCP
{
"mcpServers": {
"swih-mistral-mcp": {
"command": "npx",
"args": [
"-y",
"mistral-mcp@1.0.0"
],
"env": {
"MISTRAL_API_KEY": "YOUR_MISTRAL_API_KEY_HERE"
}
}
}
}
Frequently asked questions
1c Rest MCP is categorized under Other Tools and Integrations and uses a local stdio subprocess. Mistral MCP belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick 1c Rest MCP for other tools and integrations work and Mistral MCP 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. Mistral MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 swih-mistral-mcp 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. Mistral MCP has 65/100 (Great) with 2 views, 0 installs and 15 GitHub stars.