TMCP MCP server

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/ADAPTIVEPACKETRUNTIME.md for the adaptive packet runtime design.

Quickstart

From a TMCP checkout or plugin root:

node scripts/tmcp_launcher.mjs doctor
node scripts/tmcp_launcher.mjs status
node scripts/tmcp_launcher.mjs compose-packet "Improve this agent run" --project-path . --phase start
node scripts/tmcp_launcher.mjs harvest skills --limit 5 --no-write-artifacts
node scripts/tmcp_launcher.mjs recommend skills --candidate-workflows release_readiness --candidate-workflows developer_experience --min-confidence 0.1 --compose --no-write-artifacts

With no arguments, the same launcher starts the MCP stdio server:

node scripts/tmcp_launcher.mjs

Install Layouts

• Skill-only install: copy skills/tmcp into 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 doctor from the checkout root.
• Codex plugin cache: install as a Codex plugin; MCP config launches relative scripts/tmcp_launcher.mjs from the plugin root.
• Shared local runtime: install a verified archive with scripts/tmcp_runtime.mjs so all agent hosts use one pinned active release with offline rollback. See Central runtime.
• Deprecated AIOS compatibility: requires both TMCPENABLEDEPRECATEDAIOSADAPTER=1 and AIOS_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, and dx-audit are stable routing packages.
• Curated workflow templates: release-readiness and dx-audit are the stable templates in the recommendation catalog.
• MCP tool contracts: doctor, status, explain, compose-packet, and runtime-next are 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

Shortened. The full README is on GitHub.