metool-mcp
MCP (Model Context Protocol) server for metool - a shell environment incubator.
Features
This MCP server provides AI assistants with tools to manage metool repository manifests and synchronization:
Tools
- install_or_update_metool - Install or update metool on your system
- setup_project_standards - Set up standard conventions and AI docs for a project
- add_repo_entry - Add repository entries to .repos.txt files
- sync_directory - Run
mt syncto clone/update repositories and create symlinks - list_repos - List repositories from .repos.txt files
Prompts
- setup_metool - Guide for setting up metool on a new system
- project_setup - Guide for setting up a new project with standards
- conventions_add - Guide for adding conventions repositories
- manage_repos - Comprehensive guide for repository management
Resources
- repos-file - Access contents of repos.txt files
Installation
Via uvx (recommended)
uvx install metool-mcp
Via pip
pip install metool-mcp
From source
git clone https://github.com/mbailey/metool.git
cd metool/mcp
pip install -e .
Usage
With Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"metool": {
"command": "uvx",
"args": ["metool-mcp"]
}
}
}
Slash Commands
After configuring, you can use these commands in Claude:
/metool:setup-metool- Install or update metool on your system/metool:project-setup- Set up a new project with conventions and AI docs/metool:conventions-add mbailey/conventions- Add conventions to your project/metool:manage-repos- Get help managing repository files
Example Workflow
-
Set up a new project with standards:
/metool:project-setupThis will automatically:
- Add mbailey/conventions and mbailey/ai_docs to .repos.txt
- Run
mt syncto clone and create symlinks - Set up docs/conventions/ and docs/ai_docs/ directories
-
Add a specific conventions repository:
/metool:conventions-add mbailey/conventionsThis will:
- Add "mbailey/conventions docs/conventions" to .repos.txt
- Run
mt syncto clone and symlink the repository
-
Add custom repositories:
# The MCP server can help you: - Add entries to .repos.txt - Sync to clone/update repositories - List current repository configuration
Requirements
- Python 3.10+
- Git for repository operations
- metool - Can be installed via the MCP server's
install_or_update_metooltool
Development
# Install in development mode
cd metool/mcp
pip install -e .
# Run tests
pytest
# Run the server directly
python -m metool_mcp.server
License
Same as metool - see main repository for license information.
Release files for metool-mcp 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| metool_mcp-0.2.3.tar.gz | 33.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| metool_mcp-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.4 kB
Release files / metool_mcp-0.2.3.tar.gz
| Download URL | metool_mcp-0.2.3.tar.gz |
|---|---|
| Size | 33.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0be534079d9e889a969e605fc07417264c1176d2bc7868895c79f13a2767e36f
|
|
BLAKE2b-256 checksum How to use checksums |
c1309e4db24d0ab733d1481fc3b4dfeef3359ef37d7747f84193d4433d52247b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 5, 2025.
Transparency logRelease files / metool_mcp-0.2.3-py3-none-any.whl
| Download URL | metool_mcp-0.2.3-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b4b5c5505a8621f33698d51d0ca97fd72c7e3005c7c7b313b123d0429923000b
|
|
BLAKE2b-256 checksum How to use checksums |
b96b14890483802f44723892e213ea3c87bab9d459c389fa57a2b825233b5f9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 5, 2025.
Transparency log