Persistent cloud workspaces for AI agents: run commands, edit files, use git and a browser.
Shardflux is an MCP integration. Persistent cloud workspaces for AI agents: run commands, edit files, use git and a browser.
The registry lists a streamable-http connection at https://mcp.shardflux.dev/mcp.
The published npm package is @shardflux/mcp, version 0.12.2. Its declared MCP transport is stdio.
The package declares SHARDFLUX_API_KEY (required): Scoped Shardflux project API key (sfk_ _ ). Its tool permissions decide which workspace tools are listed.; SHARDFLUX_API_URL: API base URL. Plain http:// is allowed only for loopback hosts.; SHARDFLUX_WORKSPACE_KEY: Pin one workspace: workspace_key becomes optional on every tool and any other key is refused (workspace_pinned).; SHARDFLUX_TEMPLATE: Default template slug for workspace_open.; SHARDFLUX_MCP_TOOL_TIMEOUT_MS: Default and maximum deadline per tool call in milliseconds (1000-3600000). A call's timeout_ms can only shorten it.; SHARDFLUX_WAKE: on: workspace tools resume a suspended workspace and then run. off: they return the workspace_not_running refusal.; SHARDFLUX_WAKE_TIMEOUT_MS: Longest wait per tool call for a workspace to wake or finish a transition, in milliseconds (1000-3600000; clamped to SHARDFLUX_MCP_TOOL_TIMEOUT_MS).; SHARDFLUX_AGENT_LABEL: Attribution label of every tool token this server obtains (shown as an agent session).; SHARDFLUX_MCP_LOG_LEVEL: Log level of the JSON log lines on stderr (stdout carries the protocol).; SHARDFLUX_HTTP_KEEPALIVE: Unset: private HTTP/1.1 pooling on Node 26, native fetch elsewhere. 0: force connection closure for diagnosis. 1: select native pooling.; SHARDFLUX_PREWAKE: Offer explicit workspace_hint for tool input streaming (on or off)..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project website. This profile uses version 0.12.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related browser automation MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| SHARDFLUX_API_KEY | Scoped Shardflux project API key (sfk_ _ ). Its tool permissions decide which workspace tools are listed. | Yes |
| SHARDFLUX_API_URL | API base URL. Plain http:// is allowed only for loopback hosts. | Check documentation |
| SHARDFLUX_WORKSPACE_KEY | Pin one workspace: workspace_key becomes optional on every tool and any other key is refused (workspace_pinned). | Check documentation |
| SHARDFLUX_TEMPLATE | Default template slug for workspace_open. | Check documentation |
| SHARDFLUX_MCP_TOOL_TIMEOUT_MS | Default and maximum deadline per tool call in milliseconds (1000-3600000). A call's timeout_ms can only shorten it. | Check documentation |
| SHARDFLUX_WAKE | on: workspace tools resume a suspended workspace and then run. off: they return the workspace_not_running refusal. | Check documentation |
| SHARDFLUX_WAKE_TIMEOUT_MS | Longest wait per tool call for a workspace to wake or finish a transition, in milliseconds (1000-3600000; clamped to SHARDFLUX_MCP_TOOL_TIMEOUT_MS). | Check documentation |
| SHARDFLUX_AGENT_LABEL | Attribution label of every tool token this server obtains (shown as an agent session). | Check documentation |
| SHARDFLUX_MCP_LOG_LEVEL | Log level of the JSON log lines on stderr (stdout carries the protocol). | Check documentation |
| SHARDFLUX_HTTP_KEEPALIVE | Unset: private HTTP/1.1 pooling on Node 26, native fetch elsewhere. 0: force connection closure for diagnosis. 1: select native pooling. | Check documentation |
| SHARDFLUX_PREWAKE | Offer explicit workspace_hint for tool input streaming (on or off). | Check documentation |
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Enables AI-powered applications to monitor and interact with browser data via a Chrome extension and MCP.
Automates browsers and APIs, enabling Large Language Models (LLMs) to interact with web pages for tasks like screenshot capture and JavaScript