onec-odata-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ONEC_BASE_URL | No | Base URL of the 1C OData endpoint (e.g. https://1c.example.com/your_db/odata/standard.odata) | |
| ONEC_DATABASE | No | Database name (optional) | |
| ONEC_PASSWORD | No | Password for OData authentication | |
| ONEC_USERNAME | No | Username for OData authentication | |
| ONEC_CONFIG_PATH | No | Path to a JSON config file with baseUrl, username, password (alternative to individual env vars) | |
| ONEC_METADATA_CACHE_TTL_MS | No | Cache TTL in milliseconds for metadata (optional, default 3600000) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| odata_configA | Check 1С OData configuration status and setup instructions |
| odata_list_entitiesB | List all available OData entities from 1С |
| odata_metadataA | Get entity types and entity sets from 1С metadata (cached, TTL default 1h) |
| odata_explain_entityB | Describe entity fields, types, keys and navigation properties from metadata |
| odata_build_queryA | Build validated OData query parameters from structured intent (filters, date period, sort, top). Returns params for odata_query + human explanation. |
| odata_queryA | Query 1С OData entity with filter, select, top, orderBy, expand. Example: entity="Catalog_Контрагенты" filter="Description eq 'ООО Ромашка'" |
| odata_countB | Count records in an OData entity, optionally with filter |
| odata_financial_summaryA | Auto-detect common 1С financial entities (счета, реализации, контрагенты, заявки) and show counts |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
All eight tools have clearly distinct purposes: building query parameters, counting records, explaining entity fields, summarizing financial entities, listing entities, retrieving metadata, checking configuration, and executing queries. There is no overlap or ambiguity between tools.
All tools use the consistent 'odata_' prefix in snake_case, but the second part mixes verbs (build, count, explain, list, query) and nouns (config, financial_summary, metadata). A fully consistent pattern would use verbs consistently (e.g., odata_get_config, odata_get_metadata).
With 8 tools, the set is well-scoped for interacting with 1C OData services. It covers listing, querying, metadata retrieval, configuration check, and specialized financial summarization without being bloated or too sparse.
The set covers core read operations (list, query, count, metadata, config) and adds a specialized financial summary. Missing are create/update/delete operations, but these may be out of scope. A minor gap is the lack of a direct 'get entity by ID' tool, though query with filter can achieve this.