The TinyCloud MCP server exposes a small set of canonical CLI operations to
Model Context Protocol clients over local stdio. It pins one TinyCloud profile
when the process starts and uses delegated authority by default.
@tinycloud/mcp is a private beta and is not published to npm yet. The client
configuration below applies after package publication is approved.
Requirements
- Node.js 20 or newer
- A TinyCloud CLI profile
- An MCP client that supports local stdio servers and structured tool results
After installing @tinycloud/mcp, add a local stdio server to your MCP client:
The server captures the selected profile at startup. Restart it to select a
different profile. Delegation imports persist, so retry can happen in the same
process or a later one.
These tools use the same versioned operation contracts as the CLI projections.
Results use one of four statuses: ok, authority_required, setup_required,
or error.
Delegated secret flow
- Call
tinycloud_secrets_get with the secret name and scope.
- If the result is
authority_required, use its structured request and
approval action to obtain the exact capabilities. The server never silently
falls back to owner authority.
- Import the approved delegation with
tinycloud_auth_import.
- Retry
tinycloud_secrets_get. Requests are persisted so approval and retry
can happen in separate client sessions.
- If the result is
setup_required, follow its Secret Manager action to add
the missing value, then retry.
Secret values appear only in the structured result, not in the text result,
TinyCloud logs, errors, request files, or delegation files. Your MCP client may
retain structured results in its own transcript, so use a client and retention
policy appropriate for secrets.
Owner profiles
Owner-profile data access is disabled by default. To opt in, select the profile
explicitly and pass both flags:
Use this mode only when the MCP host should have the owner’s full authority.
Omitting either flag keeps owner data execution closed.