SharetoBoard
Cloud MCP · shriMCP

Secure remote access for approved Poppy workflows.

shriMCP is the cloud connection for supported remote clients and SharetoBoard apps. It is designed to give each app and user only the access they actually need.

Cloud staging comes next. The core service and security work are in place, but shriMCP is not publicly deployed. Live staging and Poppy acceptance must pass before beta access opens.

What shriMCP is for

Remote AI clients

Connect supported clients that cannot—or should not—launch a local TentaClaw process.

SharetoBoard apps

Give approved Android, Chrome, BoardCue, and future utilities their own controlled connection instead of embedding one shared key.

User-controlled access

Limit apps to approved boards, chats, tools, and usage. Access can be changed or revoked without exposing the Poppy key.

A separate cloud product

TentaClaw remains local. shriMCP remains cloud. They solve different connection problems and can coexist.

What remains before beta access

Built
  • Cloud gateway and runtime
  • Authentication and per-app identities
  • Board and chat permissions
  • Usage limits, revocation, and audit controls
  • Security tests and build verification
Next
  • Authorized Cloudflare staging deployment
  • Live sign-in and account testing
  • Bring-your-own-key and sponsored-access acceptance
  • Live Poppy workflow testing
  • Production operations and onboarding
See detailed shriMCP statusCompare local and cloud MCP