Froglet

What Froglet MCP server does

Froglet MCP server connects an MCP-capable agent to Froglet’s provider and runtime model. The integration registers one tool, froglet, rather than exposing a separate MCP function for every marketplace operation. Its headline workflow is marketplace_publish: an agent can turn a request to publish a service into a call to the Froglet node’s publishing path.

The wider Froglet system lets nodes publish resources, discover available services, invoke remote resources, and compose services backed by bot-authored projects, explicit source, or prebuilt artifacts. It supports named services, data-backed services, and open-ended compute addressed through a provider identifier or URL. The hosted trial includes free demonstration services such as demo.add, demo.echo, demo.fetch-witness, demo.hash-verify, and demo.notarize.

How it works

The MCP package is published as froglet-mcp and can be started with npx froglet-mcp. Behind the MCP surface, the publishing flow shells out to froglet-node publish, which is also the CLI path used by human operators. This keeps agent-driven and manual publication on the same implementation path.

Froglet nodes can operate as providers, runtimes, or both. A provider publishes resources and handles execution; a runtime can consume remote resources. The reference binary is froglet-node, and the normal dual-role configuration allows one installation to publish local resources and invoke remote ones.

Hosted use is limited to the public trial contract. Session tokens for try.froglet.dev authorize runtime deal creation and deal lookup, while the trial’s canonical proof flow uses demo.add to demonstrate discovery, a deal, a result, and a receipt. Optional witness, hash-verification, and notarization services provide additional evidence paths.

Setup and configuration

The quickest local entry point is the repository’s agent bootstrap:

curl -fsSL https://froglet.dev/agent | bash

The bootstrap installs a signed froglet-node, starts provider and runtime components from published GHCR images, writes MCP configuration, and places the installation under ~/.froglet/agent. The MCP publication flow can handle later payment and public-registration steps after local health checks.

For a source build, the project lists Rust 1.91 or newer, Python 3.12 or newer for tests, and Node 18 or newer for MCP setup and integration tests. Docker Compose v2 is supported for container-based operation. The repository also provides a signed-binary installer and a disposable-host smoke-test script.

Direct node execution uses environment settings such as FROGLET_NODE_ROLE, FROGLET_PAYMENT_BACKEND, FROGLET_LIGHTNING_MODE, and FROGLET_PRICE_EXEC_WASM. A marketplace endpoint can be selected with FROGLET_MARKETPLACE_URL. These settings apply to node and operator configuration rather than being stated as mandatory MCP variables.

Tools and capabilities

Froglet MCP server provides access to the single froglet agent tool. Supported workflows described by the project include:

• Publishing a service through marketplace_publish.
• Discovering published resources.
• Invoking remote services and compute providers.
• Running hosted demonstration proofs.
• Producing or checking signed execution evidence, including receipts and optional witness, hash, and notarization follow-ups.
• Planning local installation and provider/runtime setup through the agent-oriented installation path.

Limitations and notes

The hosted trial is free-only and does not establish paid payment rails, persistent identity, marketplace depth, service publication, or general runtime access. Payment adapters include Lightning, Stripe, and x402, but the README states that only Lightning currently extends into the standardized signed quote, deal, and invoice-bundle flow.

Self-hosted providers can register with a public HTTPS URL, a Tor v3 onion URL, or a claimed *.providers.froglet.dev hostname. The first-party hosted trial does not publish an onion endpoint unless that endpoint is separately deployed and verified. Marketplace policy, ranking, incentives, and brokerage are outside the protocol core.