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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pyrfor/onec-odata-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server