DaJet MCP Server
A DaJet Metadata based MCP server that exposes 1C metadata structure and runs SELECT queries against the database
- 26 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- execute_query runs agent-composed queries against a real database
- Database connection credentials are stored in an unencrypted config file
Install
- Works in
- Services
Manual install
docker pull zhichkin/dajet-mcp-server && docker run --name dajet-mcp-server --user=root -it -p 5000:5000 zhichkin/dajet-mcp-serverRuns in Docker on Windows or Linux.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- execute_query runs agent-composed queries against a real database
- Database connection credentials are stored in an unencrypted config file
This is third-party code. Review the repository files before installing.
What it does
The server is written in C# and built on the DaJet Metadata library; it reads 1C:Enterprise 8 metadata together with the real table and field names in the database. It is configured through datasources.json, which lists connections to several databases at once, and an agent addresses each by name. MCP tools: listing metadata type names, listing databases, resetting the cache, describing a database, getting a database's full metadata structure, searching objects by a name fragment, getting an object by type and name or by numeric code, resolving UUIDs to object names, and execute_query, which runs a parameterized SELECT in DaJet Script and returns the result as JSON. It installs from a binary release for .NET 10 or as a Docker Hub image, and runs on Windows and Linux.
Who it is for. For 1C developers and integrators who need an agent to understand the real table structure of a specific database and read data directly with SQL-like queries.
Good fit when
- You need an agent to see actual DBMS table and field names, not just 1C metadata objects
- You need agent access to several 1C databases at once by source name
- Read-only access via SELECT is enough, without writing to the database
Not a fit when
- Arbitrary agent-issued SELECT queries against a production database are not acceptable
- You have neither .NET 10 nor the ability to use Docker
- You need to write data, not just read it and read metadata
Example request
Find the Nomenclature catalog structure in the MS_TEST database and select the first record with code 333MCP
- Transport
- http
- Authentication
- not required
Limitations
execute_query runs a query that the agent itself composes, and the README does not describe a hard limit on result size. Database connection strings, including credentials, are stored in the plain datasources.json file. The README only shows connecting the MCP server in Cursor; the default HTTP address and port come from appsettings.json.
How to disable. Stop the DaJet.Mcp.Server.exe process or the container with docker rm -f dajet-mcp-server, and remove the server from your client's mcp.json.
FAQ
Can several databases be connected at once?
Yes, datasources.json supports a list of sources, and an agent addresses the one it needs by name.
Can execute_query change data?
No, the README describes it as running an arbitrary parameterized SELECT, meaning read-only.
Discussion
No questions or reviews yet.
Related
All 1C:Enterprise tools1C metadata MCP server
1C_MCP_metadata
An MCP server over a 1C extension's HTTP service that exposes configuration metadata, searches objects and validates query syntax
1C metadata MCP proxy (adapted fork)
1C_MCP_SERVER_OWN
A Python proxy between an MCP client and a 1C HTTP service: reads metadata, object structure and predefined data, with optional OAuth2
A single-binary Go MCP server: the agent sees 1C metadata, searches code, runs read-only queries and writes accurate BSL
A free MCP server for a working 1C infobase: the agent reads data from plain requests and gets the metadata structure of any configuration
A Docker server with a read-only core and pluggable modules: metadata, code, forms and relations of several 1C configurations through one MCP contract
1C OData MCP with a JSON cache
MCP сервер для работы с OData 1C
A Python MCP server over 1C OData: reads and changes catalogs and documents, saving everything to JSON files for local analysis without repeat queries
README in short
The README describes installing via a .NET 10 binary release or Docker Hub, configuring the server address in appsettings.json and data sources in datasources.json, a sample mcp.json config for Cursor, a table of nine MCP tools with parameters, an execute_query example in DaJet Script with parameters, and supported parameter data types. It states the functionality is based on the DaJet Metadata library and is similar to DaJet HTTP Server.