# mcptail - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for mcptail. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0002` supported 0.86

## What It Can Do

- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0001` supported 0.86

## How to Start

- `npx mcptail init     # wraps every MCP server in your client configs (backup kept)` Evidence: `README.md` Claim: `clm_0003` supported 0.86
- `npx mcptail ui       # → http://localhost:4747` Evidence: `README.md` Claim: `clm_0004` supported 0.86
- `npx mcptail init      wrap every stdio MCP server in detected client configs` Evidence: `README.md` Claim: `clm_0005` supported 0.86
- `npx mcptail ui        dashboard at http://localhost:4747 (--port to change)` Evidence: `README.md` Claim: `clm_0006` supported 0.86
- `npx mcptail doctor    check taps, configs, and recorded sessions` Evidence: `README.md` Claim: `clm_0007` supported 0.86
- `npx mcptail remove    unwrap everything, restoring original configs` Evidence: `README.md` Claim: `clm_0008` supported 0.86
- `npx mcptail run -- <command>   the wrapper itself (init injects this)` Evidence: `README.md` Claim: `clm_0009` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Sandbox-trial permissions first
- **Why**: The project has signals of install commands, host configuration, or local writes; do not go straight into your primary environment—trial it in isolation first.

### 30-Second Read

- **What to do now**: Sandbox-trial permissions first
- **Minimum safe next step**: Run Prompt Preview first; if you still want to install, trial only in an isolated environment
- **Do not trust yet**: Tool permission boundaries cannot be trusted before install.
- **Continuing will touch**: Command execution, Local environment or project files, Host AI context

### What You Can Trust Now

- **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0002` supported 0.86
- **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0001` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0003` supported 0.86

### What You Cannot Trust Yet

- **Tool permission boundaries cannot be trusted before install.** (unverified): MCP/tool projects usually touch files, the network, the browser, or external APIs, so permissions and logs must be checked for real.
- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior.
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md`

### What Continuing Will Touch

- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md`
- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0010` inferred 0.45
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0011` supported 0.86
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0001` supported 0.86

### Context Scale

- Total files: 36
- Important-file coverage: 35/36
- Evidence index entries: 35
- Role / Skill entries: 4

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for mcptail, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat mcptail as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for mcptail, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 4 role / Skill / project-doc entries.

- **🔍 mcptail** (project_doc): See what your AI agent is actually doing. One command. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **Contributing to mcptail** (project_doc): Thanks for helping make MCP traffic visible. PRs of every size are welcome — the fastest reviews go to small, focused changes. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CONTRIBUTING.md`
- **Roadmap** (project_doc): v0.2 ships the core loop: tap → record → inspect → replay, stdio-only, three clients. Everything below is up for grabs — comment on the linked issue before starting so work doesn't collide. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `ROADMAP.md`
- **Code of Conduct** (project_doc): This project follows the Contributor Covenant v2.1 https://www.contributor-covenant.org/version/2/1/code of conduct/ . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `CODE_OF_CONDUCT.md`

## Evidence Index

- Indexed 35 evidence entries.

- **🔍 mcptail** (documentation): See what your AI agent is actually doing. One command. Evidence: `README.md`
- **Package** (package_manifest): { "name": "mcptail", "version": "0.2.0", "description": "See what your AI agent is actually doing. Passive traffic capture, token attribution, and replay for MCP servers — one command.", "keywords": "mcp", "modelcontextprotocol", "observability", "debugging", "proxy", "ai-agents", "claude", "cursor", "developer-tools" , "homepage": "https://github.com/Neal006/mcptail", "repository": { "type": "git", "url": "git+https://github.com/Neal006/mcptail.git" }, "bugs": "https://github.com/Neal006/mcptail/issues", "license": "MIT", "author": "Neal006", "type": "module", "engines": { "node": " =20" }, "bin": { "mcptail": "dist/cli.js" }, "files": "dist" , "scripts": { "build": "tsup && vite build ui"… Evidence: `package.json`
- **Contributing to mcptail** (documentation): Thanks for helping make MCP traffic visible. PRs of every size are welcome — the fastest reviews go to small, focused changes. Evidence: `CONTRIBUTING.md`
- **License** (source_file): Copyright c 2026 Neal006 and mcptail contributors Evidence: `LICENSE`
- **Roadmap** (documentation): v0.2 ships the core loop: tap → record → inspect → replay, stdio-only, three clients. Everything below is up for grabs — comment on the linked issue before starting so work doesn't collide. Evidence: `ROADMAP.md`
- **Cli** (source_file): import { Command } from "commander"; import pkg from "../package.json" with { type: "json" }; import { runProxy } from "./proxy.js"; import { startDashboard } from "./server.js"; import { listSessions, sessionsRoot } from "./store.js"; import { type FileResult, initTaps, removeTaps, tapStatus } from "./taps.js"; ⋮---- function printResults results: FileResult , verb: string : void Evidence: `src/cli.ts`
- **Cost** (source_file): export function estimateTokens value: unknown : number Evidence: `src/cost.ts`
- **Frames** (source_file): export type JsonRpcMessage = { key: string : unknown }; ⋮---- export type Frame = { kind: "json"; msg: JsonRpcMessage } { kind: "raw"; raw: string } { kind: "blank" }; ⋮---- export function parseFrame line: string : Frame ⋮---- export class LineSplitter ⋮---- push chunk: Buffer : string ⋮---- flush : string null Evidence: `src/frames.ts`
- **Proxy** (source_file): import type { Readable, Writable } from "node:stream"; import spawn from "cross-spawn"; import { LineSplitter, parseFrame } from "./frames.js"; import { SessionWriter } from "./store.js"; ⋮---- export interface ProxyOptions { server?: string; input?: Readable; output?: Writable; } ⋮---- export function runProxy command: string , opts: ProxyOptions = ⋮---- const tee = splitter: LineSplitter, dir: "c2s" "s2c", chunk: Buffer : void = Evidence: `src/proxy.ts`
- **Replay** (source_file): import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js"; import { z } from "zod"; ⋮---- export interface ReplayResult { ok: boolean; result?: unknown; error?: string; } ⋮---- export async function replayCall command: string , method: string, params: unknown, : Promise Evidence: `src/replay.ts`
- **Server** (source_file): import { existsSync, readFileSync, statSync } from "node:fs"; import { createServer, type IncomingMessage, type ServerResponse } from "node:http"; import { extname, join, resolve } from "node:path"; import { fileURLToPath } from "node:url"; import { replayCall } from "./replay.js"; import { aggregate, correlate, listSessions, readEvents, sessionsRoot } from "./store.js"; ⋮---- function uiDir : string ⋮---- function safeSessionFile raw: string null : string null ⋮---- function json res: ServerResponse, status: number, body: unknown : void ⋮---- function sessionDetail file: string ⋮---- export function createDashboardServer ⋮---- // ponytail: 500ms size polling instead of fs.watch — identical… Evidence: `src/server.ts`
- **Store** (source_file): import { appendFileSync, mkdirSync, readdirSync, readFileSync } from "node:fs"; import { homedir } from "node:os"; import { join } from "node:path"; import { estimateTokens } from "./cost.js"; import type { Frame, JsonRpcMessage } from "./frames.js"; ⋮---- export interface SessionMeta { type: "meta"; server: string; command: string ; startedAt: number; pid: number; } ⋮---- export interface TapEvent { ts: number; dir: "c2s" "s2c"; frame: Frame; } ⋮---- export function mcptailHome : string ⋮---- export function sessionsRoot : string ⋮---- function dateDir ts: number : string ⋮---- export class SessionWriter ⋮---- constructor meta: Omit ⋮---- write event: TapEvent : void ⋮---- private disable… Evidence: `src/store.ts`
- **Taps** (source_file): import { copyFileSync, existsSync, readFileSync, writeFileSync } from "node:fs"; import { adapters } from "./adapters/index.js"; ⋮---- interface ServerEntry { command?: string; args?: string ; key: string : unknown; } ⋮---- export function isWrapped entry: ServerEntry : boolean ⋮---- export function wrapEntry name: string, entry: ServerEntry : boolean ⋮---- export function unwrapEntry entry: ServerEntry : boolean ⋮---- export interface FileResult { client: string; path: string; changed: string ; skipped: string ; error?: string; } ⋮---- function applyToFile client: string, path: string, serversKey: string, transform: name: string, entry: ServerEntry = boolean, backup: boolean, : FileResult… Evidence: `src/taps.ts`
- **Claude Code** (source_file): import { join } from "node:path"; import { type ClientAdapter, userHome } from "./types.js"; ⋮---- candidates cwd Evidence: `src/adapters/claude-code.ts`
- **Cursor** (source_file): import { join } from "node:path"; import { type ClientAdapter, userHome } from "./types.js"; ⋮---- candidates cwd Evidence: `src/adapters/cursor.ts`
- **Index** (source_file): import { claudeCode } from "./claude-code.js"; import { cursor } from "./cursor.js"; import type { ClientAdapter } from "./types.js"; import { vscode } from "./vscode.js"; Evidence: `src/adapters/index.ts`
- **Types** (source_file): import { homedir } from "node:os"; ⋮---- export function userHome : string ⋮---- export interface ConfigCandidate { path: string; serversKey: string; } ⋮---- export interface ClientAdapter { name: string; candidates cwd: string : ConfigCandidate ; } ⋮---- candidates cwd: string : ConfigCandidate ; Evidence: `src/adapters/types.ts`
- **Vscode** (source_file): import { join } from "node:path"; import type { ClientAdapter } from "./types.js"; ⋮---- candidates cwd Evidence: `src/adapters/vscode.ts`
- **Api** (source_file): export interface SessionInfo { file: string; server: string; command: string ; startedAt: number; pid: number; } ⋮---- export interface Call { id: string number; method: string; toolName?: string; request: unknown; response?: unknown; isError: boolean; startTs: number; latencyMs?: number; requestTokens: number; responseTokens: number; } ⋮---- export interface ToolStats { key: string; count: number; errors: number; p50LatencyMs: number; p95LatencyMs: number; tokens: number; } ⋮---- export interface SessionDetail { file: string; calls: Call ; notificationCount: number; rawCount: number; stats: ToolStats ; totalTokens: number; } ⋮---- export const fetchSessions = : Promise ⋮---- export const f… Evidence: `ui/src/api.ts`
- **App** (source_file): import { useEffect, useMemo, useState } from "preact/hooks"; import { type Call, fetchSession, fetchSessions, postReplay, type ReplayResponse, type SessionDetail, type SessionInfo, subscribeLive, } from "./api.js"; ⋮---- const time = ts: number const day = ts: number ⋮---- setSelected s.file ; setCall null ; ⋮---- ⋮---- ⋮---- <button type="button" class="copy" onClick= Evidence: `ui/src/app.tsx`
- **Main** (source_file): import { render } from "preact"; import { App } from "./app.js"; Evidence: `ui/src/main.tsx`
- **Style** (source_file): :root { ⋮---- { ⋮---- body { ⋮---- .layout { ⋮---- header { ⋮---- header .logo { ⋮---- header .live-dot { ⋮---- header .spacer { ⋮---- header select { ⋮---- aside { ⋮---- aside h2, ⋮---- .session { ⋮---- .session:hover { ⋮---- .session.active { ⋮---- .session .name { ⋮---- .session .when { ⋮---- main { ⋮---- .tiles { ⋮---- .tile { ⋮---- .tile .value { ⋮---- .tile .value.err { ⋮---- .tile .label { ⋮---- table { ⋮---- th { ⋮---- td { ⋮---- td.num { ⋮---- tr.call { ⋮---- tr.call:hover td { ⋮---- tr.selected td { ⋮---- .status { ⋮---- .status.err { ⋮---- .status.pending { ⋮---- .detail { ⋮---- .detail .close { ⋮---- .detail h3 { ⋮---- .detail .meta { ⋮---- .detail h4 { ⋮---- .detail pre { ⋮----… Evidence: `ui/src/style.css`
- **Code of Conduct** (documentation): This project follows the Contributor Covenant v2.1 https://www.contributor-covenant.org/version/2/1/code of conduct/ . Evidence: `CODE_OF_CONDUCT.md`
- **Biome** (structured_config): { "$schema": "https://biomejs.dev/schemas/2.5.2/schema.json", "files": { "includes": "src/ ", "tests/ ", "ui/src/ ", " .json", " .ts" }, "formatter": { "enabled": true, "indentStyle": "space", "indentWidth": 2, "lineWidth": 100 }, "linter": { "enabled": true, "rules": { "preset": "recommended" } }, "javascript": { "formatter": { "quoteStyle": "double" } } } Evidence: `biome.json`
- **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "NodeNext", "moduleResolution": "NodeNext", "lib": "ES2022" , "strict": true, "noUncheckedIndexedAccess": true, "noImplicitOverride": true, "verbatimModuleSyntax": true, "resolveJsonModule": true, "skipLibCheck": true, "noEmit": true, "types": "node" }, "include": "src", "tests" , "exclude": "node modules", "dist", "ui" } Evidence: `tsconfig.json`
- **Tsconfig** (structured_config): { "compilerOptions": { "target": "ES2022", "module": "ESNext", "moduleResolution": "bundler", "lib": "ES2022", "DOM", "DOM.Iterable" , "strict": true, "jsx": "react-jsx", "jsxImportSource": "preact", "noEmit": true, "skipLibCheck": true }, "include": "src" } Evidence: `ui/tsconfig.json`
- **.editorconfig** (source_file): charset = utf-8 end of line = lf insert final newline = true indent style = space indent size = 2 Evidence: `.editorconfig`
- **.gitattributes** (source_file): text=auto eol=lf .png binary .gif binary Evidence: `.gitattributes`
- **Secrets** (source_file): Secrets .env .env. !.env.example .pem .key Evidence: `.gitignore`
- **.nvmrc** (source_file): 22 Evidence: `.nvmrc`
- **Demo** (source_file): $ npx mcptail init + wrapped github claude-code: .mcp.json + wrapped firecrawl claude-code: .mcp.json + wrapped postgres cursor: ~/.cursor/mcp.json $ npx mcptail ui mcptail dashboard: http://localhost:4747 mcptail ● live CALL LATENCY TOKENS TIME firecrawl · scrape 1.2s 3,410 14:02:11 github · create pr error -32602 212 14:02:13 postgres · query 86ms 1,882 14:02:15 ▶ replay · copy request · export Evidence: `docs/demo.svg`
- **Tsup.Config** (source_file): import { defineConfig } from "tsup"; Evidence: `tsup.config.ts`
- **Index** (source_file): mcptail 🔍 " / Evidence: `ui/index.html`
- **Vite.Config** (source_file): import preact from "@preact/preset-vite"; import { defineConfig } from "vite"; Evidence: `ui/vite.config.ts`
- **Vitest.Config** (source_file): import { defineConfig } from "vitest/config"; Evidence: `vitest.config.ts`

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `package.json`, `CONTRIBUTING.md`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `package.json`, `CONTRIBUTING.md`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Introduction and Quickstart**: importance `high`
  - source_paths: README.md, ROADMAP.md, CONTRIBUTING.md, package.json
- **System Architecture and Data Pipeline**: importance `high`
  - source_paths: src/frames.ts, src/proxy.ts, src/taps.ts, src/store.ts, src/cost.ts
- **Client Adapters and Configuration Management**: importance `high`
  - source_paths: src/adapters/index.ts, src/adapters/types.ts, src/adapters/claude-code.ts, src/adapters/cursor.ts, src/adapters/vscode.ts
- **Dashboard, Replay, and Common Operations**: importance `high`
  - source_paths: src/server.ts, src/replay.ts, ui/src/app.tsx, ui/src/api.ts, ui/src/main.tsx

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `6af3b59a37d3bf50ceaebfea43d47aa1465fc3be`
- inspected_files: `README.md`, `package.json`, `src/adapters/claude-code.ts`, `src/adapters/cursor.ts`, `src/adapters/index.ts`, `src/adapters/types.ts`, `src/adapters/vscode.ts`, `src/cli.ts`, `src/cost.ts`, `src/frames.ts`, `src/proxy.ts`, `src/replay.ts`, `src/server.ts`, `src/store.ts`, `src/taps.ts`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: Adapter: Cline
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Adapter: Cline. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may misconfigure credentials, environment, or host setup: Adapter: Cline
- Evidence: failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/8
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: Adapter: Windsurf
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Adapter: Windsurf. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may misconfigure credentials, environment, or host setup: Adapter: Windsurf
- Evidence: failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/6
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: Adapter: Zed
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Adapter: Zed. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may misconfigure credentials, environment, or host setup: Adapter: Zed
- Evidence: failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/7
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Configuration risk requires verification

- Trigger: Developers should check this configuration risk before relying on the project: Streamable HTTP / SSE transport capture
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Streamable HTTP / SSE transport capture. Context: Source discussion did not expose a precise runtime context.
- Why it matters: Developers may misconfigure credentials, environment, or host setup: Streamable HTTP / SSE transport capture
- Evidence: failure_mode_cluster:github_issue | https://github.com/Neal006/mcptail/issues/18
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/Neal006/mcptail
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.