Set up an agent

One prompt sets up any agent that can fetch a URL. Plugins and one-click installs cover the rest.

Agents publish through the same REST API and CLI as humans do. For any agent that can fetch a URL and act on it, setup is one prompt:

Teach any agent to publish

That page teaches the agent to publish with a single HTTP request, without a Model Context Protocol (MCP) server or the CLI. An agent with no tools at all learns to tell the user what unlocks publishing instead of improvising.

Some agents have a better path than the prompt: a plugin, a one-click install, or hosted MCP. Each agent’s page under spacefast.com/setup has the exact paste, click, or command.

Install the CLI

The CLI covers everything an agent needs, from incremental publishes to logs and diagnostics.

npm install -g spacefast

pnpm add -g spacefast

npm install -g spacefast

bun add -g spacefast

For a standalone binary, download the asset for your platform plus checksums.txt from the public CLI releases and verify the binary’s SHA-256 before you install it.

Run the setup command

From the project where the agent will work, run:

sf setup agent

The command detects supported agents, installs the Spacefast skill, and configures MCP. Use sf setup agent -y for a non-interactive setup. The CLI reference lists every supported client and option. Cloud and browser agents that cannot run local commands use hosted MCP instead.

Supported agents

Every agent connects through one of three mechanisms:

Plugin or skill: the spacefast/plugins marketplace package, the spacefast skill, or an agent’s own plugin directory. A plugin or skill includes the publish workflow, not only the tools.
MCP: local stdio through the CLI, or hosted MCP with browser OAuth.
Deeplink: a one-click install link that prefills the hosted endpoint.

The setup index lists every supported agent. Claude Desktop installs as a one-click extension from the spacefast/plugins releases.

sf setup agent --agent configures the same clients from the terminal. github-copilot, factory-droid, gemini-cli, devin-desktop, and cline get skills plus MCP. continue is skills-only and needs --skip-mcp. Use generic for any client that reads AGENTS.md. In that command, --agent claude means Claude Code. Claude on the web and mobile connects with the connector deeplink on its setup page, and the desktop app has its own page. Any other agent that can fetch a URL can use hosted MCP or the HTTP publish flow.

Install only the skill

For agents that support skills, install the official skill without the rest of the setup:

npx -y skills add spacefast/plugins --skill spacefast -g -y

Confirm the install with sf skills status. Raw skill Markdown is available at https://api.spacefast.com/skill for agents that only support fetch-and-import flows. The skill gives agents the publish workflow, space-state rules, claim-link handling, and Spacefast file conventions.

Docs as Markdown

Every developer page is available as plain Markdown. To get the exact Markdown source, append .md to any URL (for example https://spacefast.com/docs/cli.md or https://spacefast.com/docs/errors/rate_limited.md). Requests from known AI-agent user agents, and requests whose Accept header prefers Markdown, receive that form at the HTML URL automatically.

Machine-readable docs discovery lives at llms.txt and llms-full.txt. Product-level discovery lives on the product origin:

MCP covers the MCP server card and endpoint.

The generated OpenAPI spec at https://api.spacefast.com/openapi.json describes the full API.

Your own published spaces can serve agents the same way with an Agent=true redirect condition.

Auth and accounts

Interactive humans use sf login. CI uses a masked ci_deploy API key stored as a token:

sf login --token sfa_123

Hosted agents use MCP OAuth or a dashboard handoff link redeemed with sf login --handoff.

Handoff links

The dashboard can mint a one-use handoff link for an agent or machine. Redeem the link through stdin, never through argv:

printf '%s\n' "$HANDOFF_LINK" | sf login --handoff

Agent accounts

For durable automation, create an agent account instead of sharing a broad personal API key. Scope the account to the teams and capabilities it needs. Create one in the dashboard under Settings → Developer → Agents. Agent accounts authenticate with OAuth private_key_jwt, and the CLI or on-device MCP loads them through SPACEFAST_AGENT_CONFIG. See API keys for presets and rotation.

Secret handling

Treat space keys (sfc_...), upload tokens, device codes, API keys, share-link URLs, and .spacefast state as credentials. Do not print, commit, archive, or include them in logs and chat, and avoid shell tracing when secrets are present. Pass credentials through the environment or the target platform’s secret store, and clear temporary copies after use.

Publish as an agent: the curl flow, receipts, and claim handling.
MCP: hosted and on-device MCP, tools, and resources.