Shardflux

Lets an assistant work inside persistent Shardflux cloud workspaces: running commands, editing files, using git and a browser.

What it does

Shardflux exposes persistent cloud workspaces to an AI assistant as MCP tools. According to the registry description, an assistant can run commands, edit files, and use git and a browser inside those workspaces. Workspaces can be opened from a template, resumed when suspended, and pinned to a single workspace key. Tool permissions attached to the API key determine which workspace tools are listed.

When to use it

Worth adding when an assistant needs a durable remote environment for coding or shell work rather than the local machine, for example running commands, editing files, committing with git, or driving a browser in a workspace that persists between sessions.

Requirements

Runs locally as a stdio process via npx from the npm package @shardflux/mcp, so Node.js is needed. Requires a scoped Shardflux project API key in SHARDFLUX_API_KEY; optional variables cover the API base URL, workspace key, template, wake behaviour, timeouts, logging and an agent attribution label. Desktop only; network access to the Shardflux API is required.