mcp
Use VDO.Ninja WebRTC data channels, or a self-hosted HTTP relay, as MCP tools for bot-to-bot messaging, reliable file transfer, and shared state, with clear transport limits, optional TURN, and optional join-token/session-MAC security.
소스 정보
- 저장소
- steveseguin/ninjamcp
- 최근 소스 활동
- 2026년 10월 21일 05:42
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- mcp
- description
- Use VDO.Ninja WebRTC data channels, or a self-hosted HTTP relay, as MCP tools for bot-to-bot messaging, reliable file transfer, and shared state, with clear transport limits, optional TURN, and optional join-token/session-MAC security.
# VDO.Ninja MCP Skill
Use this skill to run VDO.Ninja as an MCP data bridge in Codex, Claude Code, and compatible MCP clients.
## What It Is For
- Fast bot-to-bot data messaging.
- Reliable file send/receive over WebRTC data channels.
- Optional secure room membership and peer allowlists.
## What It Is Not
- Not a generic TCP tunnel.
- Not guaranteed firewall bypass.
## Core Transport Truth
- Default transport is WebRTC data channels.
- `transport: "http"` uses a self-hosted, encrypted HTTP relay when WebRTC cannot run or connect. Both peers must choose the same transport; there is no automatic failover.
- TURN can improve success on restrictive networks.
- TURN is not guaranteed to bypass all enterprise policies.
## Fast Path
1. Install MCP registration:
`npm i @vdoninja/mcp`
2. Register for Codex/Claude:
`npx vdon-mcp-install`
3. Start server:
`npx vdon-mcp-server`
If run directly in a terminal, it prints a short running banner and a first-call hint.
4. Optional least-privilege tool profile:
`VDON_MCP_TOOL_PROFILE=core|file|state|full npx vdon-mcp-server`
5. First tool call:
`{ "name": "vdo_capabilities", "arguments": {} }`
## Two Primary Workflows
### Workflow A: Messaging
- Connect peer A and peer B with `vdo_connect`.
- Send with `vdo_send`.
- Receive with `vdo_receive`.
- Demo script: `npx vdon-mcp-demo-message`
### Workflow B: File Transfer
- Send with `vdo_file_send` or `vdo_file_send_path`.
- Track with `vdo_file_transfers`.
- Read with `vdo_file_receive` or persist with `vdo_file_save`.
- Resume interrupted send with `vdo_file_resume`.
- Demo script: `npx vdon-mcp-demo-file`
## Security Controls
- `join_token` + `join_token_secret`
- `enforce_join_token`
- `allow_peer_stream_ids`
- `require_session_mac`
For secure presets, set `VDON_MCP_JOIN_TOKEN_SECRET` before install/runtime.
`@vdoninja/mcp` depends on `@vdoninja/sdk`, so SDK installs transitively.
## AI Agent Contract
- Call `vdo_capabilities` first.
- Call `vdo_connect` before send/file/state tools.
- Prefer least-privilege tool profile.
- For files, use file tools instead of manual chunking via `vdo_send`.
- Handle `validation_error` and retry idempotently.
## Testing
Tests ship in the repository, not the npm package. From a checkout:
- Product test bar: `npm run test:mcp`
- Full engineering suite: `npm run test:mcp:all`
- Live diagnostics (optional): `references/advanced-diagnostics.md`
## References
- Optional SSApp download and remote setup: [SSApp guide](references/ssapp-integration.md) ([HTML](docs/ssapp-integration.html))
- Operator quickstart: `references/quickstart-and-compat.md`
- HTTP relay setup: `references/http-relay.md`
- Client config examples: `references/client-config-examples.md`
- Tool contract: `references/mcp-tool-contract.md`
- Transport notes: `references/vdo-ninja-p2p-data-notes.md`
- Registry manifest: `server.json`
GitHub에서 보기