ML Training Init MCP Server
A Model Context Protocol (MCP) server that implements a sequential thinking pattern for ML training script generation with managed file constraints.
Key Feature: Managed File System (1 Training + 2 Configs)
IMPORTANT: This server enforces a managed file constraint system:
- 1 Training Script: The main ML training file that will be executed
- Up to 2 Config Files: Optional configuration files (YAML, JSON, .env, etc.)
- ALL operations work only with these managed files
- Prevents agents from creating unnecessary files when stuck
- Clearly identifies ML training workflows with [ML TRAINING WORKFLOW] tags
Installation
pip install -r requirements.txt
Running the Server
python -m src.server
Usage with Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"ml-training-init": {
"command": "python",
"args": ["-m", "src.server"],
"cwd": "/path/to/ml-training-init-mcp"
}
}
}
Available Tools
1. initialize_training_file
- Creates the main training script file
- Takes: file_name, content, reference
- Returns: file_path, file_type, managed_files status
- AI agents use this for ML training workflows
2. create_config_file
- Creates configuration files (max 2 allowed)
- Supports: YAML, JSON, TOML, .env, .ini, etc.
- Takes: file_name, content, config_type
- Returns: file_path, file_type, managed_files status
3. get_managed_files
- Lists all managed files (training + configs)
- Shows file paths and names
- Returns: training file info, config files list
4. get_file_content
- Get content of a specific managed file
- Takes: file_name
- Returns: file_path, content, file_type
5. get_current_file
- Quick access to training file content
- Returns: file_path, content
6. monitor_and_fix
- Fix errors in any managed file
- Takes: error_trace, file_name (optional)
- Auto-parses common Python/ML errors
Testing
Run the test example:
python test_example.py
This will show you how to interact with the MCP server through Claude.
Metadata
Release files for ml-training-init-mcp 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ml_training_init_mcp-0.2.2.tar.gz | 18.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ml_training_init_mcp-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.4 kB
Release files / ml_training_init_mcp-0.2.2.tar.gz
| Download URL | ml_training_init_mcp-0.2.2.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcc31ae8f584089c71b1e48b907d7b2580c1e8e09676661ca34323b362e5c211
|
|
BLAKE2b-256 checksum How to use checksums |
291e99e8fd75047c0c1fcb51d6e71c0e5f5235e9d2fff115f829752bf7430d1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.6
|
Release files / ml_training_init_mcp-0.2.2-py3-none-any.whl
| Download URL | ml_training_init_mcp-0.2.2-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9eede76ac5506ff7f246f50667360b2bdf48b265f7844f547952934e7174a12
|
|
BLAKE2b-256 checksum How to use checksums |
9fbabf173a2e7ea113afadc5fcd70a10acc59ec0f6e912b1c200731d66601cda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.6
|
Security for ml-training-init-mcp 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.