Skip to content
Monolythium docs
GitHub

Connect an agent to Stele

Preview

Stele has two separate MCP profiles. The hosted profile is the supported public-web companion with an OAuth-authorized runtime inventory. The local lyth_mcp prerelease has exactly three read/status tools. Neither profile has wallet-key, signing, transaction, booking, payment, or settlement authority.

Hosted OAuth profile

Section titled “Hosted OAuth profile”

The production resource is https://stele.monolythium.com/mcp. It has been exercised end to end with Codex CLI 0.144.1 and Claude Code 2.1.211, including dynamic client registration, PKCE, browser-wallet consent, token exchange, exact tool discovery, and a real stele_search_services call.

Codex

Section titled “Codex”
Terminal window
codex mcp add stele --url https://stele.monolythium.com/mcp
codex mcp login stele
codex mcp list

Claude Code

Section titled “Claude Code”
Terminal window
claude mcp add --transport http stele https://stele.monolythium.com/mcp
claude mcp login stele
claude mcp list

Login opens Stele’s OAuth and wallet-consent flow in the browser. Use a wallet with domain-bound wallet-auth v1; it is available in the v0.4.5 browser-wallet GitHub prerelease, while Chrome Web Store publication remains pending. Review the requested stele:public:read and stele:drafts:write scopes before approving. The wallet proof creates an application session and OAuth grant only; it is not a transaction signature and cannot move value.

After login, the authenticated tools/list response is authoritative for the hosted inventory; do not infer a fixed tool count from this page. These deployed operations remain part of the hosted surface:

Tool Authority
stele_search_services Search the public Stele catalog
stele_create_booking_draft Create a short-lived, nonbinding, non-economic draft for wallet-owned review

Only when the authenticated tools/list response includes the exact stele_create_provider_listing_draft name may a client call that tool. Each successful create operation produces exactly one new private, wallet-owned, unpublished provider-listing draft. An idempotent replay returns that same draft without creating another. If the name is absent, the operation is unavailable. It is create-only: it cannot list, read, update, delete, or publish an existing draft, and it cannot sign, submit, or settle a transaction.

Production search returned 0 published services during the July 16, 2026 release validation. The booking-approval draft tool is deployed but cannot currently produce a successful booking-approval draft because it requires a real published listing; unknown or unavailable listings fail closed. Private provider-listing drafts from the web Studio do not satisfy that prerequisite, and neither MCP profile can list, read, update, delete, or publish an existing draft. If a listing is published later, its review page still cannot approve a booking, contact a provider, reserve service, sign, submit, broadcast, pay, or lock funds. Do not paste access tokens, wallet secrets, or recovery material into a prompt or MCP configuration.

Local exact-three profile

Section titled “Local exact-three profile”

The reviewed local profile is available in the lyth_mcp v0.1.0 GitHub prerelease. It requires Node.js 22 or newer. Download the versioned archive and its verification material before installing anything:

Terminal window
mkdir lyth-mcp-0.1.0
cd lyth-mcp-0.1.0
base=https://github.com/monolythium/lyth_mcp/releases/download/v0.1.0
for asset in lyth-mcp-0.1.0.tgz lyth-mcp-0.1.0.spdx.json SHA256SUMS lyth-mcp-0.1.0.tgz.cosign.bundle; do
  curl --fail --location --remote-name "$base/$asset"
done


sha256sum --check SHA256SUMS
cosign verify-blob \
  --bundle lyth-mcp-0.1.0.tgz.cosign.bundle \
  --certificate-identity https://github.com/monolythium/lyth_mcp/.github/workflows/release.yml@refs/tags/v0.1.0 \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  lyth-mcp-0.1.0.tgz


npm install --global --ignore-scripts ./lyth-mcp-0.1.0.tgz

Both verification commands must succeed before the local npm install step. On macOS, use shasum -a 256 --check SHA256SUMS in place of sha256sum. The release page also provides cosign bundles for SHA256SUMS and the SPDX SBOM.

Codex local profile

Section titled “Codex local profile”

Register the isolated executable, then verify the configured server:

Terminal window
codex mcp add stele-local -- lyth-stele-mcp
codex mcp list

Claude Desktop local profile

Section titled “Claude Desktop local profile”

Add this entry to Claude Desktop’s MCP configuration and restart the application:

{
  "mcpServers": {
    "stele-local": {
      "command": "lyth-stele-mcp"
    }
  }
}

Do not add wallet-store, passphrase, signing, or submission environment variables to this isolated profile.

Verify the exact-three boundary

Section titled “Verify the exact-three boundary”

The local profile exposes exactly three read/status tools:

Tool Authority
stele_connection_status Re-read and compare SDK, network-identity, and Stele metadata
stele_search_services Search public Stele listings after a fresh identity check
stele_agent_wallet_status Report that the dedicated-agent-wallet boundary is unavailable without opening a key

The local profile cannot access, create, reveal, or unlock a wallet key. It cannot prepare, sign, submit, or broadcast a transaction, create a booking draft, book, pay, reserve service, or lock funds. Do not paste a seed, private key, mnemonic, passphrase, access token, or other credential into a model prompt.

Hosted OAuth never expands the local profile. The runtime-discovered hosted inventory and fixed local exact-three inventory are separate authority boundaries; configuring both does not combine their tools or grant transaction authority.

Next

Section titled “Next”