- The CLI — for terminal agents (Claude Code, shell loops, CI): push folders, pull them back, mint share links. Full reference: cli.md.
- The MCP endpoint — for MCP hosts (claude.ai connectors, Claude
Desktop, Claude Code, any MCP client): 41
slideless_tools over streamable HTTP at/mcp. Full reference: mcp-connector.md.
The CLI
Get the binary (npm i -g @antasphere/slideless, or a workspace build):
slideless.antasphere.com): one command, with
your Antasphere account. The CLI runs on the cloud by default, so it needs no
URL:
slk_ API key server-side (scopes presentations:read +
presentations:write) and stores it on the instance’s profile in
~/.config/antasphere/tools/slideless.json (mode 600; the shared Antasphere
CLI config home, see cli.md). That profile becomes the
active one, so later commands need no URL.
Sign in on a self-hosted instance, with a pasted key (works with
EMAIL_DRIVER=none, and required for accounts with 2FA). Mint the key in the
dashboard: API keys, then Create key. Tick presentations:write there
(the dialog pre-selects presentations:read only) so the key can push and
share; the secret is shown once, right after creation. Then:
AGENT.md), from which the agent fetches only what it needs; see
Share links, read by agents. The model is in the Concepts pages, starting with
The deck is the artifact.
push is content-addressed (only missing blobs upload; a re-push of the
same folder is a new immutable version), the first push writes
.slideless.json into the folder so later pushes target the same deck, and
--json on any command but files download emits the wire shape for machine parsing. See
cli.md for sharing flags (expiry, password, pin-to-version),
collaborator grants, annotations export, and slideless dev (a local
preview server with the exact viewer sandbox headers).
The MCP endpoint
Every instance serves MCP at:/mcp accepts the instance’s
slk_ keys directly, no OAuth dance:
/mcp body cap — tools answer a clean “use the CLI” error for bigger
decks.
Verify an instance end to end:
Scopes and revocation
Machine credentials reach only the endpoints consciously allowlisted for
their scopes (fail-closed — see security.md); member
deactivation is re-checked on every request, so cutting a person off cuts
their agents off in the same moment.