Stelaspace Mcp

io.github.StelaSpacePublished by GitHub account StelaSpacev1.0.3Updated Oct 24, 2026

Publish AI-generated HTML (dashboards, reports, docs) to permanent, sandboxed, shareable links.

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A local MCP server that lets coding agents publish HTML files from disk to StelaSpace as permanent, sandboxed, shareable links.

What you can do
Publish an HTML file by path to a StelaSpace space, with optional title, slug, tags and visibility, returning a permanent URL; reusing a slug publishes a new version of the same document. List the spaces available in your team. List and search documents within a space.
When to use it
Use it when an agent such as Claude Code or Codex generates dashboards, reports or docs as HTML files on disk and you want them published as shareable links, including large files over 1 MB that are too big to pass as tool arguments.
Requirements
Runs locally over stdio, typically via npx, so Node.js is needed. Requires a StelaSpace API key in the STELASPACE_API_KEY environment variable, created in StelaSpace under Settings then API Keys. Network access to the StelaSpace API is required; STELASPACE_API_URL can override the endpoint. Claude Desktop chat is not supported for publishing.
Before you install
The API key is a secret passed in the environment; keep it out of shared configs and repositories. Publishing uploads file contents to StelaSpace and creates links that may be public depending on the visibility you choose, and reusing a slug replaces the published version. Review what is published before sharing.

Installation

In SourceWeft

  1. Open Stelaspace Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

stelaspace-mcp

[stelaspace-mcp MCP server]

A local MCP server for publishing HTML files to StelaSpace from coding agents that work with your local files — Claude Code and Codex.

It runs on your machine, so it reads HTML files directly from disk by path and uploads the bytes via the StelaSpace API. That's what lets it publish large (1 MB+) reports and dashboards — unlike passing file contents as a tool argument, which is capped by the model's output size.

Claude Desktop (chat) isn't supported for publishing: its sandbox can't share files with a local MCP server, so it can't upload local reports. Use Claude Code or Codex, where the agent generates the report to disk and publishes it directly.

Tools

  • publish_file — { path, spaceSlug, title?, slug?, tags?, visibility? } → reads the file and returns its permanent URL. Reusing a slug publishes a new version.
  • list_spaces — list the spaces in your team.
  • list_documents — { spaceSlug, query? } — list documents in a space.

Setup

Get an API key from StelaSpace → Settings → API Keys (starts with ss_sk_).

Claude Code

bash
claude mcp add stelaspace --scope user \  --env STELASPACE_API_KEY=ss_sk_your_key \  -- npx -y stelaspace-mcp

Codex

~/.codex/config.toml:

toml
[mcp_servers.stelaspace]command = "npx"args = ["-y", "stelaspace-mcp"]env = { STELASPACE_API_KEY = "ss_sk_your_key" }

Then ask the agent to build and publish a report, e.g. "generate the sales dashboard and publish the HTML to my reports space as public."

Environment

  • STELASPACE_API_KEY (required) — your ss_sk_ key.
  • STELASPACE_API_URL (optional) — override the API endpoint. Defaults to https://stelaspace.com; most users never need to set this.

Source: README.md at commit f199828

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts