Developer · Local MCP server
Watch Cli
Hand any social video to your AI agent — frames + transcript bundled. MCP server for watch-cli.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.sonpiaz/watch-cli- Version
- 0.3.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-20
- Updated
- 2026-05-20
- Publisher
- sonpiaz (GitHub) · 2 servers with pages here
- Repository
- github.com/sonpiaz/watch-cli (folder mcp-server)
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @sonpiaz/watch-cli-mcp | 0.3.1 | stdio |
How to connect Watch Cli
Watch Cli runs locally from a Node.js package published to the npm registry: @sonpiaz/watch-cli-mcp version 0.3.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @sonpiaz/watch-cli-mcp@0.3.1. It reads these environment variables: KYMA_API_KEY (secret), GROQ_API_KEY (secret) and WATCH_AUDIO_MODE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"watch-cli": {
"command": "npx",
"args": [
"-y",
"@sonpiaz/watch-cli-mcp@0.3.1"
],
"env": {
"KYMA_API_KEY": "<secret>",
"GROQ_API_KEY": "<secret>",
"WATCH_AUDIO_MODE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from sonpiaz (GitHub)
| Server | Runs |
|---|---|
| Openaffiliate MCPSearch and discover affiliate programs with agent-ready data and commission details. | Remote & Local · HTTP, stdio |
More developer servers
| Server | Runs |
|---|---|
| Warp OzbridgeOzBridge: run Warp Oz agents from any MCP client — Claude Code, Cursor, Codex, VS Code. | Local · SSE |
| WarpwebResearch, build, and deploy AI-generated websites via the Warpweb API. | Local · stdio |
| Wasabi MCPMCP server for Wasabi buckets and objects via S3. Needs access keys. | Local · stdio |
| wasm-mcpRead-only MCP server for the WebAssembly spec: instructions, types, sections, search, proposals. | Remote & Local · HTTP, stdio |
| WatchpupFree uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts. | Remote · HTTP |
| Water Quality PortalWater Quality Portal (WQP) MCP — US ambient water-chemistry monitoring. | Remote · HTTP |
| Watson OrchestrateManage IBM Watson Orchestrate tools, agents, connections from Cursor, Copilot, Claude. | Local · stdio |
| WaveHouse CloudBrowse, query, and administer your managed WaveHouse + ClickHouse projects (schema, pipes, policy). | Remote · HTTP |