TentaClaw docs · local-only 0.3.0rc13 private beta

Install one local MCP server. Connect the clients on that computer.

TentaClaw supports local MCP over stdio only. The MCP client starts the process automatically; TentaClaw reads its per-user configuration, enforces approved Poppy destinations, and exits with the client.

Start local setup Choose a client

Overview Install Skills Tools Security Clients Troubleshooting Release

Local-only architecture

Local MCP client ↓ starts a child process over stdio TentaClaw on this computer ↓ fixed-host authenticated HTTPS Poppy API

Not included: remote MCP, HTTP listeners, OAuth, bearer tokens, domains, tunnels, reverse proxies, Docker hosting, VPS/cloud deployment, or a managed TentaClaw service.

Requirements

Python 3.10-3.13

Install only the exact checksummed RC13 release bundle with its bundled platform installer.

Your own Poppy access

A Poppy subscription and API key are separate requirements controlled by Poppy.

A local MCP client

The exact product surface must start a local stdio command and show approval before every write tool.

Normal local workflow

Install: verify tentaclaw-mcp-0.3.0rc13-release.zip with its companion .sha256 file and run the bundled installer.
Configure: run tentaclaw-mcp init, enter the Poppy key through hidden terminal input, and explicitly select board/chat pairs.
Verify: run tentaclaw-mcp status and tentaclaw-mcp doctor.
Connect: use codex-config install/check for Codex-backed clients; use client-config <client> for another candidate client.
Test: confirm six tools, approval before every write call, and a disposable Poppy destination before production data.

Local files and credential boundary

`config.json`

Contains non-secret limits and explicit board/chat IDs. New destinations remain denied until setup is rerun.

`poppy_api_key`

Contains only the Poppy credential. POSIX ownership/mode/symlink checks are enforced; Windows setup applies an owner-only ACL.

Client configuration contains neither file: the generated MCP entry contains only the executable command and arguments.

Six tools

Tool	Purpose	Effect
`tentaclaw_version`	Return local version, `stdio`, and local-only status.	Local read
`poppy_get_boards`	List policy-approved Poppy boards.	Poppy read
`poppy_get_chats`	List approved chat assistants and their nested conversations for one approved board.	Poppy read
`poppy_ask`	Ask one bounded question.	May consume credits
`poppy_create_conversation`	Create a persistent conversation.	Creates Poppy state
`poppy_chat`	Continue an approved conversation.	May consume credits/save history when requested

Four first-party skills

Skills teach a local agent when and how to use TentaClaw. They never own the Poppy key, read its file, make direct Poppy HTTP requests, or add a remote transport.

`tentaclaw-setup`

Local setup, diagnosis, rotation, incident response, and migration.

`poppy-operator`

Exact destinations, bounded questions, conversation control, and fail-closed behavior.

`poppy-board-research`

Focused research from one approved board/chat.

`poppy-content-workflow`

Brainstorm, create, and rewrite work requiring human review.

Local client targets

RC13 has a guarded Codex install/check/remove workflow and candidate configuration generators for Claude Desktop, Claude Code, Gemini CLI, Perplexity Mac local MCP, and MCP Inspector. Gemini CLI 0.52.0 has passed the read-only live path; full write approval remains open. OpenClaw and Hermes templates are not shipped because their generic MCP paths lack the required write-action approval gate.

Open client-specific guidance →

Before wider release

Complete live Poppy and exact-client acceptance on the unchanged RC13 candidate.
Complete clean-machine verification.
Merge the approved candidate and create the signed release provenance.
Require independent GitHub attestation verification before running any downloaded public artifact.