SharetoBoard
Planned free/open-source project · v0.3.0 release candidate

Give your AI agent a focused route into Poppy.

Tentaclaw is the MCP Server. It translates six structured tool calls into controlled Poppy API requests. Four first-party skills teach compatible agents how to set it up, choose approved destinations, research, and draft without ever owning the Poppy key.

Read the Tentaclaw docs Ask about release testing
Current status: Draft PR #1 contains six MCP tools, four skills, stronger local controls, native client examples, 24 tests across Python 3.10-3.12, a clean production dependency audit, deterministic artifacts, SBOM, and verified checksums. Review/merge approval, live Poppy acceptance, client-specific validation, final artifact approval, tag, and public publication remain open.
How it fits

A separate agent path—not a Chrome Pro dependency.

Chrome Pro opens Poppy chatbot links in Chrome. Tentaclaw is the MCP Server that connects external agent clients to the documented Poppy API. First-party skills run in the agent environment and call Tentaclaw tools; they are not a second server.

Agent runtime + first-party skillsChooses safe workflows and sends structured MCP tool calls
Tentaclaw MCP ServerOwns the credential, policy checks, and six Poppy tools
Poppy APIReceives HTTPS requests for boards, chats, and conversations

Exact path: Agent runtime + SharetoBoard/Tentaclaw skills → MCP → Tentaclaw MCP Server → HTTPS → Poppy API.

First-party agent kit

Four skills, each with a narrow job.

tentaclaw-setup

Safe installation, verification, rotation, incidents, and migration.

poppy-operator

Core board/chat resolution, bounded use, and conversation control.

poppy-board-research

Focused, source-aware research from one approved destination.

poppy-content-workflow

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

Credential rule: skills use Tentaclaw MCP tools only. They do not contain the key, read the key file, or make direct Poppy HTTP calls.

Read the skills manualRead the white paper
Verified in the current code

Six focused MCP tools.

The current implementation exposes exactly these operations. It does not claim broader Poppy board construction or commercial account governance.

poppy_get_boards

List boards available to the configured Poppy API key.

poppy_get_chats

List chat assistants for a selected board.

poppy_create_conversation

Create a conversation for a board and chat assistant.

poppy_ask

Ask a one-time question without a conversation thread.

poppy_chat

Continue an existing Poppy conversation.

tentaclaw_version

Report the running Tentaclaw version.

Security posture

Local stdio release path. The agent never owns the key.

stdio is the default

No inbound network port is required for an agent running on the same machine.

Poppy secrets stay outside prompts

The preferred setup reads the Poppy API key from a restricted file. POSIX permissions are checked by the current implementation.

No public listener in v0.3.0

The release CLI is stdio-only. Any future remote mode requires a separately authenticated, TLS-protected gateway; raw public exposure is not a release feature.

Important: A secret file is still plaintext protected by operating-system permissions. Use a secrets manager, container secret, or vault when your deployment supports one.

Product boundary

What Tentaclaw is—and what it is not.

Tentaclaw is

  • A free SharetoBoard technical project
  • An unofficial MCP server for the Poppy API
  • A local stdio server by default
  • A stdio-only release CLI in v0.3.0
  • A bring-your-own Poppy subscription and API-key tool
  • Designed for MCP-compatible agent environments

Tentaclaw is not

  • SharetoBoard Chrome Pro
  • A billing system or customer portal
  • A credit, throttle, entitlement, or usage ledger
  • A multi-account router or reseller dashboard
  • A white-label managed Poppy service
  • A claim that every MCP client has completed acceptance testing

API Conduit is separate: customer identities, credits, rate limits, revocation, billing, multi-account routing, reseller controls, and audit ledgers belong to a different future infrastructure product—not Tentaclaw.

Compatibility posture

Designed for MCP-compatible environments. Validation is evidence-gated.

Draft PR #1 now contains client-native candidate examples for Codex, Claude, OpenClaw, and Hermes. Those examples establish the intended configuration shape; no client will be labeled “tested” until its exact-version end-to-end run is recorded.

Review tools, transports, and release gates Back to the SharetoBoard ecosystem