turn-mcp

Category: Data & AI | Uploader: shiahonb777 | Downloads: 0 | Version: v1.0（Latest）

You have access to `turn.wait` (aliases: `turn_wait`, `turn`). Use it to communicate with the human at every step.

Changelog: Source: GitHub https://github.com/shiahonb777/turn-mcp

Directory Structure

Current level: Root

📁 .github/
- 📁 ISSUE_TEMPLATE/
  - 📄 bug_report.yml 1.8 KB
  - 📄 feature_request.yml 1.4 KB
- 📁 workflows/
  - 📄 ci.yml 922 B
📁 examples/
- 📁 python/
  - 📄 langchain_tool.py 1.9 KB
  - 📄 langgraph_checkpoint.py 2.9 KB
  - 📄 plain_asyncio.py 1.3 KB
  - 📄 README.md 642 B
📁 public/
- 📄 app.js 69.4 KB
- 📄 i18n.js 15.2 KB
- 📄 index.html 12.9 KB
- 📄 manifest.json 267 B
- 📄 styles.css 55.4 KB
- 📄 sw.js 2.4 KB
📁 python-client/
- 📁 turn_mcp_client/
  - 📄 __init__.py 270 B
  - 📄 client.py 7.3 KB
- 📄 pyproject.toml 960 B
- 📄 README.md 2.5 KB
📁 src/
- 📄 auto-configure.ts 14.5 KB
- 📄 config.ts 5.7 KB
- 📄 event-log.ts 4.0 KB
- 📄 history-persistence.ts 2.0 KB
- 📄 server-stdio.ts 571 B
- 📄 server.ts 33.5 KB
- 📄 sse-manager.ts 1.7 KB
- 📄 turn-mcp-server.ts 6.9 KB
- 📄 wait-store.ts 13.8 KB
- 📄 webhook.ts 3.9 KB
📁 tests/
- 📄 ui-events-auth-visibility.test.js 2.7 KB
- 📄 ui-events-entry-prune-hint.test.js 2.5 KB
- 📄 ui-events-filter-interactions.test.js 2.4 KB
- 📄 ui-history-filter-interactions.test.js 3.5 KB
- 📄 ui-pagination-interactions.test.js 4.1 KB
- 📄 ui-smoke-runner-cli.test.js 3.0 KB
- 📄 ui-smoke-runner.js 11.6 KB
- 📄 ui-test-harness.js 11.8 KB
- 📄 wait-store.test.js 13.7 KB
📄 .dockerignore 53 B
📄 .gitignore 336 B
📄 .npmignore 500 B
📄 CONTRIBUTING.md 2.3 KB
📄 docker-compose.yml 702 B
📄 Dockerfile 404 B
📄 LICENSE 1.1 KB
📄 package-lock.json 40.6 KB
📄 package.json 1.6 KB
📄 README.md 9.1 KB
📄 README.zh-CN.md 8.2 KB
📄 SKILL.md 1.5 KB
📄 SKILL.zh-CN.md 1.5 KB
📄 start.bat 2.8 KB
📄 start.command 4.9 KB
📄 start.sh 4.9 KB
📄 tsconfig.json 388 B

SKILL.md

# turn-mcp-web Skill

You have access to `turn.wait` (aliases: `turn_wait`, `turn`). Use it to communicate with the human at every step.

## What it does

Calling `turn.wait` pauses you, sends your message to the human's browser, and blocks until they reply. One API session becomes an unlimited back-and-forth conversation. **Never end the loop yourself** — keep calling after every action until the human says stop.

## Call format

```
turn.wait(
  context   = "What you did + what you're about to do",   # required
  question  = "The specific thing you need from them",     # optional
  options   = ["Option A", "Option B", "Option C"],        # optional — pre-set reply buttons
  agentName = "YourName"                                   # optional
)
```

## Three techniques

**1. Pre-set replies with `options`**  
When the next step has clear branches, give the human buttons instead of making them type. They click one, you get the text back and continue.

```python
turn.wait(
  context="Found 3 stale files. Total 240 KB.",
  question="What should I do?",
  options=["Delete all", "Show me first", "Skip"]
)
```

**2. Write context for someone who wasn't watching**  
Every message is read cold. State: what you found, what you did, what comes next.

**3. Follow the suffix**  
Every reply ends with a reminder to call `turn.wait` again. Follow it — that suffix is how the session stays alive.

## The loop

```
work → turn.wait → reply → work → turn.wait → reply → ...
```

The human ends the session. You don't.

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

turn-mcp

Directory Structure

SKILL.md

Report

Notice