InnerVault

Shardflux

Stale Official MCP Registry, dev.shardflux

Persistent cloud workspaces for AI agents: run commands, edit files, use git and a browser.

Open the source (opens docs.shardflux.dev) https://docs.shardflux.dev/reference/mcp

Before you use it

  • Runs on someone else's server: what you send it leaves your machine.
  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: SHARDFLUX_API_KEY. Use a key with the least access you can.

What it is

MCP servers from dev.shardflux.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

npm package (stdio)

@shardflux/mcp@0.12.2

From the server's entry in the official MCP Registry

Remote endpoint (streamable-http)

https://mcp.shardflux.dev/mcp

From the server's entry in the official MCP Registry

Settings it asks for

  • SHARDFLUX_API_KEY secret required · Scoped Shardflux project API key (sfk_<key id>_<secret>). 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).

Related

  1. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  2. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  3. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  4. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  5. Anthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.

    Hand-checked InnerVault (hand-checked), Anthropic Anthropic documentation

  6. Playwright MCP

    MCP servers

    Lets an agent drive a real browser: open pages, click, fill in forms and read what's on screen.

    Hand-checked InnerVault (hand-checked), Microsoft Apache-2.0

    claude mcp add playwright npx @playwright/mcp@latest