TentaClaw Private Beta | Local MCP for Poppy

Private beta candidate

TentaClaw 0.3.0rc13

Core packaging, security, and cross-platform qualification have passed. Live-client and clean-machine testing continue before wider release.

Request private beta access Review release status

One product, one architecture

Local MCP client → local TentaClaw process → Poppy API.

Local MCP clientStarts TentaClaw automatically and sends structured tool calls over stdio

Local TentaClaw MCP ServerReads the protected key, applies destination policy, and exposes six tools

Poppy APIReceives fixed-host HTTPS requests for approved boards, chats, and conversations

There is no hosted TentaClaw product in this architecture: no VPS, domain, public endpoint, OAuth server, tunnel, reverse proxy, Docker deployment, or inbound MCP port.

How it works

Install locally, approve destinations, connect your client.

Join the private beta. Approved testers receive the RC13 candidate and its checksum through the private beta channel.
Run tentaclaw-mcp init. Enter the Poppy key through hidden local terminal input and choose approved boards and chats.
Run status and doctor. Confirm the protected key file, policy, and Poppy reachability without printing private data.
Connect a client. For a Codex-backed client, use tentaclaw-mcp codex-config install and check. For another candidate client, use tentaclaw-mcp client-config <client>.

Read the local setup guide Check release availability

Local client targets

Built for clients that can launch a local `stdio` command.

Private beta testing focuses on supported local stdio clients. Compatibility and approval behavior are verified per client before broader availability.

Open the local client guide See testing status

Six focused tools

A small, reviewable Poppy capability surface.

tentaclaw_version

Report the local runtime version and local-only transport status.

poppy_get_boards

List only boards permitted by the local policy.

poppy_get_chats

List approved chat assistants and their nested conversations for one approved board.

poppy_ask

Ask one bounded question; may consume Poppy credits.

poppy_create_conversation

Create a persistent conversation on an approved destination.

poppy_chat

Continue an approved conversation; history remains off unless requested.

First-party agent kit

Skills guide the workflow. TentaClaw owns the credential.

`tentaclaw-setup`

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

`poppy-operator`

Exact destination resolution, bounded use, and conversation control.

`poppy-board-research`

Focused research from one approved local destination.

`poppy-content-workflow`

Brainstorm, create, and rewrite work returned for human review.

Credential rule: skills call TentaClaw tools. They never contain the Poppy key, read the key file, make direct Poppy HTTP calls, or propose remote hosting.

Security posture

The client sees a local command and six tools—not the key.

No MCP listener

TentaClaw supports local stdio only and opens no inbound MCP network port.

Protected per-user files

The guided setup writes a separate key file and non-secret policy file. POSIX protections are verified; Windows setup applies an owner-only ACL.

Fail-closed policy

New boards and chats remain denied until the user reruns setup and explicitly approves them.

Product boundary

What TentaClaw is—and what it is not.

TentaClaw is

A free local project planned for open-source release
An unofficial MCP server for the Poppy API
A per-user stdio child process
A bring-your-own Poppy subscription and API-key tool
A six-tool server with explicit destination policy

TentaClaw is not

A hosted MCP service
A cloud server, VPS deployment, or public endpoint
An OAuth, tunnel, gateway, or remote connector product
A multi-user customer portal, billing system, or account router
A claim that every local MCP client has completed acceptance testing

Connect supported AI tools to Poppy from your computer.