This section documents how AI coding agents use Tapper as shared project memory: how to install the MCP server, how agents should orient themselves, and which conventions keep the KEG safe for humans and agents at the same time.
Vendor-specific project configuration, permission modes, and general plugin
behavior are covered by the vendors themselves. This directory focuses on
Tapper's embedded native plugins. Use tap integrate codex or tap integrate claude as the official supported installation and upgrade path; use manual MCP
configuration only for generic hosts without a native Tapper plugin.
- Claude Code Plugin — install tapper as a bundled
Claude Code plugin: one command to register the MCP server and the
tapperskill. - Codex plugins — install baseline
tapperand optionaltapper-devfrom the embedded local marketplace. - Orientation Surface — the shared
orientpayload exposed by themcp__tapper__orienttool, thetapper://orientresource, andtap orient. - MCP Server Setup — manual setup for hosts that do not use
a bundled integration:
claude mcp add, JSON config for arbitrary MCP clients, and the tool categories exposed over MCP. - Provider-neutral launcher composition — future immutable
--flightprocess binding across agent hosts and runtimes. - Agent Conventions — tapper invariants every agent should follow: MCP-first, never edit node files directly, never mix CLI writes with a live MCP session, snapshot before destructive edits.
| You want to… | Read |
|---|---|
| Install tapper in Claude Code in one command | Claude Code Plugin |
| Install tapper in Codex in one command | Codex Install |
| Understand the orientation payload | Orientation Surface |
| Wire tapper into a non-bundled MCP host | MCP Server Setup |
| Know which tools the MCP server exposes | MCP Server Setup — Available Tools |
| Tell an agent how to behave against a KEG | Agent Conventions |