compose4mcp: docker compose for 1C MCP
compose4mcp
A set of ready docker-compose configs for running various 1C-ecosystem MCP servers
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- Brings up Docker containers that may connect to the 1C database and outside network
- Connection secrets live in a local .env, and the user is responsible for protecting them
Install
Manual install
docker compose up -dRun inside the chosen service folder under src/, after renaming .env.example to .env and filling in the variables.
This is third-party code. Review the repository files before installing.
What it does
The repository collects sample docker-compose.yaml files for several independent 1C-related MCP servers: code checking, configuration metadata, platform help, syntax checking, template search and a separate MCP SSL server. Each service has its own folder with docker-compose.yaml and .env.example. A user copies the needed folder, renames .env.example to .env, fills in the variables and starts the container with docker compose up -d. The MCP servers themselves are not developed here, only the configs to run them.
Who it is for. For 1C developers who want to quickly stand up one of the existing 1C MCP servers via Docker without building the configuration from scratch.
Good fit when
- You want to quickly stand up a 1C MCP server for code checks, metadata or help via Docker
- You need a ready docker-compose and .env template for such a server
- You already use this author's other MCP servers and want one launch pattern
Not a fit when
- You need the MCP server's own code, not just the launch configuration
- You do not use Docker or cannot run a container
Example request
Bring up the 1C code-check MCP server container from compose4mcp and connect it to Claude CodeLimitations
This is a set of configuration templates, not an MCP server: the service code comes from images that need separate review. The README does not explain where to get the images for some of the services. Secrets and connection parameters must be filled in manually in .env, and the README explicitly warns not to commit them.
How to disable. Stop the container with docker compose stop in the service folder, or remove it entirely with docker compose down.
Security check
- Brings up Docker containers that may connect to the 1C database and outside network
- Connection secrets live in a local .env, and the user is responsible for protecting them
README in short
The README explains that src/ holds docker-compose.yaml templates for various 1C MCP services that can be copied and adapted. It describes the .env.example workflow, a warning not to commit secrets, and basic docker compose commands: up, ps, logs, stop, restart, down.
FAQ
Does the repo contain the MCP servers' own code?
No, only docker-compose configs and .env examples to run them.
Which services are included?
1c-code-checker, configuration metadata, platform help, syntax checking, template search and an MCP SSL server.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
Agent Skills for Google products
Agent Skills for Google products and technologies
Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring