Agents - Spacefast DocsSkip to content
Spacefast Docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Agents

What an agent can do on Spacefast, and the three ways to connect your client to the Spacefast MCP server

Connect your coding agent to Spacefast once, then ask it to publish. This page covers what an agent can reach, the three connection lanes, and which one to pick.

What an agent can do

Anything you can do in the dashboard, an agent can do over MCP. The Spacefast MCP server exposes five tools.

  • publish uploads a folder, a file, an archive, or inline files and returns the live URL and the immutable version URL.
  • operation_status checks a publish that is still running.
  • show_space opens a read-only view of deployments, domains, analytics, source files, changes, history, comparisons, or build logs.
  • execute runs one JavaScript program against the Spacefast API catalog. Use it for documentation, account information, API reads without a visual view, and mutations.
  • resume_execution continues the same program after it pauses for your approval.

Inside execute, search for an operation with tools.search, read its contract with tools.describe, then call it. Check each write with a read before reporting success.

If your team has a saved Design System, your agent can read its standards and files while working on a project. Ask it to apply the system to a new build or bring an existing project into line with the current rules.

Publish this folder to Spacefast and give me the live URL.

Show me the deployments for this Space and whether the last build passed.

Point docs.example.com at this Space and tell me which DNS records to add.

Read the MCP server page for the tool schemas, the sandbox contract, and the approval model.

Three ways to connect

Vendor plugin

Your client’s own marketplace installs MCP config, the Spacefast skill, and any hooks in one step.

Universal installer

One npx command that writes the same plugin into any of seven supported clients.

sf setup agent

The CLI detects your installed clients, writes MCP config, and installs the skill.

Vendor plugin

Best when your client has a plugin marketplace. Claude Code, Codex, and Factory Droid each take the same repository.

claude plugin marketplace add spacefast/plugins
claude plugin install spacefast@spacefast

You get MCP config, the spacefast skill, and for Claude Code one SessionStart hook. Nothing assumes the sf CLI is installed.

Universal plugins installer

Best when your client has no marketplace of its own but does read plugin directories. Targets are claude-code, cursor, codex, github-copilot, vscode, grok, and kimi.

npx -y plugins add spacefast/plugins -t cursor -y

sf setup agent

Best when you already use the sf CLI and want the connection to ride on your CLI login instead of an editor OAuth flow. It detects installed clients, writes each one’s MCP config, and installs the skill.

npm install -g spacefast
sf setup agent

The default connection method is remote-proxy, which points your client at sf mcp proxy. See sf setup agent for every flag.

Pick your client

Claude Code

Plugin with skill, bundled scripts, and a SessionStart hook.

Codex

Plugin with skill and bash fallback scripts, or a TOML entry.

Cursor

Plugin with an always-available rule, or a one-click deeplink.

Claude Desktop

A double-click desktop extension with an optional token field.

Any other MCP client

The stdio command, the hosted URL, and generic JSON config.

Skills

What the shipped skill tells your agent, and how to install it alone.

Permissions

What an agent can never do without you, and how approvals work.

Last updated on October 8, 2026

Was this page helpful?