TMCP README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the TMCP listing page.
TMCP
Slash commands are manual imports. TMCP is the compiler.
TMCP turns scattered agent instructions into task-specific operating packets. The user describes the work in natural language. TMCP infers task identity, compiles the strongest current packet from skills/rules/evidence, recompiles as the work changes, and leaves an audit trail.
Skill names are provenance, not the user interface. Power users can still force a route; the default is natural prompting.
TMCP runs standalone from a repo checkout, copied plugin package, Codex plugin cache, Claude plugin cache, or any MCP host that can launch the bundled Node entrypoint. The former AIOS adapter is deprecated and disabled by default; AIOS_ROOT alone no longer enables it.
See docs/ADAPTIVE_PACKET_RUNTIME.md for the adaptive packet runtime design.
Quickstart
From a TMCP checkout or plugin root:
With no arguments, the same launcher starts the MCP stdio server:
Install Layouts
- Skill-only install: copy
skills/tmcpinto a skills directory. Use the skill for routing and manual packet synthesis unless the host also exposes the bundled launcher. - Repo checkout: clone the repo and run
node scripts/tmcp_launcher.mjs doctorfrom the checkout root. - Codex plugin cache: install as a Codex plugin; MCP config launches relative
scripts/tmcp_launcher.mjsfrom the plugin root. - Shared local runtime: install a verified archive with
scripts/tmcp_runtime.mjsso all agent hosts use one pinned active release with offline rollback. See Central runtime. - Deprecated AIOS compatibility: requires both
TMCP_ENABLE_DEPRECATED_AIOS_ADAPTER=1andAIOS_ROOT; new installations should use standalone TMCP.
Claude Desktop users can add the launcher as a local stdio MCP server. See docs/CLAUDE_DESKTOP.md.
Stability Scopes
TMCP labels three independent surfaces:
- Skill packages:
tmcp,skill-harvest,workflow-recommendation,release-readiness, anddx-auditare stable routing packages. - Curated workflow templates:
release-readinessanddx-auditare the stable templates in the recommendation catalog. - MCP tool contracts:
doctor,status,explain,compose-packet, andruntime-nextare stable. Harvest, evaluation, recommendation, promotion, receipt, and expert-rubric tools remain experimental.
Experimental templates and tools remain shipped and callable. They are labeled experimental in their own outputs and frontmatter so users do not confuse a stable package route with a stable tool contract or curated template.
Experimental workflows include UI rubric, security/privacy, test strategy, adaptive workflow pack, custom rubric generation, routing policy, skill gap analysis, incident postmortem, architecture decision, migration readiness, agent handoff, PR risk, performance readiness, data integrity, public-sector readiness, and repo behavior spec loop.
Tools
| Tool | Purpose |
|---|---|
tmcp_doctor | Check first-run readiness and supported install layouts. |
tmcp_status | Report standalone capability and optional AIOS adapter status. |
tmcp_explain | Compile a task-specific TMCP packet. |
tmcp_compose_packet | Compile a task/phase operating packet with task_identity, packet_markdown, and provenance. |
tmcp_runtime_next | Return packet deltas or a full recompiled packet (output_mode: full) after runtime evidence changes. |
tmcp_record_receipt | Write an advisory run receipt after verification or outcome on a secure-persistence host. |
tmcp_harvest_skills | Harvest local skills, instructions, rules, docs, and workflows into source nodes. |
tmcp_evaluate_skills | Create or score a skill-evaluation plan from full SKILL.md inputs. |
tmcp_recommend_workflows | Recommend stable or experimental workflows from harvested evidence, with stability metadata. |
tmcp_promote_harvest | Explicitly promote reviewed harvest signals into durable source-to-atom and atom-to-workflow graph artifacts. |
expert_rubric_review_plan | Produce an expertise packet, scored rubric, evidence audit, remediation plan, and verification expectations. |
Safety
Harvest redacts sensitive-looking values and secret-like provenance paths by default and treats harvested instructions as untrusted text. Default harvest behavior excludes .env*, credentials, tokens, browser profiles, private caches, dependency trees, build outputs, VCS data, and generated TMCP/AIOS artifacts. It does not follow source symlinks unless follow_symlinks is explicitly enabled; enabled links must still resolve inside the selected source root.
On hosts with secure descriptor-relative filesystem operations, harvest artifacts
are written as one staged, atomic bundle through a symlink-safe destination.
Leave output_dir unset for a unique .tmcp/harvest-* directory, or provide an
output directory that is new or empty.
Skill evaluation accepts explicit regular SKILL.md inputs, can confine them to a supplied project root, and redacts source, plan, and evidence values before deriving reports. Its initial plan artifact is a staged bundle in a new or empty directory; evidence scoring may safely add its report to that same directory.
Artifact persistence is deliberately unavailable where those secure filesystem
operations do not exist. doctor and status report the capability; use
--no-write-artifacts for portable analysis and see
Compatibility for the
boundary.
tmcp_record_receipt has no non-persisting preview because the receipt is the
artifact itself. Run it only when status reports artifact persistence
available.
Packet sessions are equally explicit: compose-packet --session-id writes one
redacted, project-local latest-packet record only when secure persistence is
available. They are for a single serialized run, not a global history or
coordination service. See the CLI session contract.
If a harvested source tries to override system, developer, or user instructions, TMCP reports a warning. See SECURITY.md.
Examples
Harvest a local skills folder:
Recommend workflows for a project:
Compose a current-task packet and recompile during the run. This session flow
requires status to report artifact persistence available:
When session persistence is unavailable, preserve the compatibility path by
passing the prior composed JSON inline through --previous-packet instead.
Legacy delta-only runtime routing:
Promote reviewed harvest signals into durable routing artifacts:
On secure-persistence hosts, promotions also persist a redacted advisory graph
under TMCP_HOME/promoted-harvests/<opaque-promotion-key>/, or
~/.tmcp/promoted-harvests/<opaque-promotion-key>/ when TMCP_HOME is unset.
Receipts live under TMCP_HOME/receipts/<yyyy-mm>/.
Global cache content is advisory and cannot override system, developer, user, or
project instructions.
Packet composition and runtime routing do not read that cache unless the caller
explicitly passes --cache-policy global; their default policy is none.
Run an expert rubric review from evidence snippets:
More examples live in examples. Developer onboarding and release readiness exercise stable curated templates; skill-harvest and recommendation examples remain available through experimental tool contracts.
Validation
Before release:
The release package check builds from a clean, reviewed Git revision rather than the working directory. It ships only an explicit allowlist of committed files, rejects unsafe paths, symlinks, and secret-like content, then emits a deterministic RELEASE_MANIFEST.json plus archive digest. The CI release gate repeats the build from the same Git tree and requires both digests to match. It also validates frontmatter, hardcoded local paths, private example names, links, extracted-package install shape, doctor, sample harvest, sample workflow recommendation, sample expert rubric planning, composition/runtime/receipt smoke coverage, and stable/experimental workflow labeling. It is a DOI blocker until existing absolute user paths in release evidence docs are redacted or normalized.
DOI-Ready Research Release
TMCP is prepared as an independent software-methods artifact. See RESEARCH_READY.md and docs/release-notes/v0.3.3-doi.md for the citable artifact boundary, validation path, data-availability policy, and claim limits.