integrated-harness-kit-mcp
An MCP server that exposes diagnostic and (in later versions) management
tools for the tot0rokr/agents
harness — the shared configuration layer for Claude Code, Codex
CLI, OpenCode, and Gemini CLI.
Install
uvx integrated-harness-kit-mcp
That command runs the server on stdio; pair it with a CLI agent's MCP
client (see the repo root's INSTALLATION.md for ready-made config
snippets per CLI).
What's available
v0.2 — read-only
| Tool | Purpose |
|---|---|
harness_status |
repo presence + state of the 5 home-dir symlinks |
doctor |
run the harness's scripts/doctor.sh and surface its output |
list_skills |
enumerate registered SKILL.md entries |
list_mcp_servers |
enumerate canonical MCP servers in shared/mcp/servers.json |
list_commands |
enumerate slash commands in shared/commands/ |
list_subagents |
enumerate sub-agents in shared/subagents/ |
Planned
- v0.3 —
clone,install,render(mutate the harness from inside a chat) - v0.4 —
add_skill,add_mcp_server,add_command,add_subagent(+remove_*) - v0.5 —
update,audit_drift,commit,edit_memory,edit_instruction
Repo discovery
Every tool resolves the agents repo in this order:
- The function's
repo_pathargument. - The
AGENTS_REPOenvironment variable. ~/agents.
A candidate is accepted only if it contains scripts/install.py.
Development
cd mcp/
python3 -m venv .venv
.venv/bin/pip install -e '.'
.venv/bin/python -m unittest discover -s tests -v
Tools live in src/integrated_harness_kit_mcp/tools/ as plain functions, so the
unit tests don't import mcp and don't depend on FastMCP behaviour.
License
MIT. See repo root.
Metadata
Release files for integrated-harness-kit-mcp 0.3.1
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 | Actions |
|---|---|---|---|---|
| integrated_harness_kit_mcp-0.3.1.tar.gz | 11.9 kB | Without provenance | Details for integrated_harness_kit_mcp-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| integrated_harness_kit_mcp-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for integrated_harness_kit_mcp-0.3.1-py3-none-any.whl |
Total release size: 24.0 kB
Release files / integrated_harness_kit_mcp-0.3.1.tar.gz
| Download URL | integrated_harness_kit_mcp-0.3.1.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1a369d05987c2ea1dcb2edb4ec09cc87fdf851e68414762630ffb8730c3d8771
|
|
BLAKE2b-256 checksum How to use checksums |
6b952d4ed73915edb4a37c5f390d7614cbdc73eea1667364ced269d527403658
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / integrated_harness_kit_mcp-0.3.1-py3-none-any.whl
| Download URL | integrated_harness_kit_mcp-0.3.1-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cdbd1685089d5119d73cc6793a2c3e9cdee1e41e5eb70ddc8c33e8bce58b504e
|
|
BLAKE2b-256 checksum How to use checksums |
a91a5264ab09bb99eb8aad813b086de56d53996fa56dc8a568e5688562d9bcb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for integrated-harness-kit-mcp 0.3.1
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.