mcpField
S
stelaspace-mcp

stelaspace-mcp

Local
github.com/StelaSpaceCloud & Infra0Updated 19w ago
Repository

About stelaspace-mcp

stelaspace-mcp is a local MCP server for Claude Code and Codex that publishes local HTML files to StelaSpace. It reads files by path and uploads their bytes, supporting large reports and dashboards.

Key features

  1. 01Reads HTML files by local path
  2. 02Publishes files and returns permanent URLs
  3. 03Publishes a new version when reusing a slug
  4. 04Lists team spaces and documents

Use cases

  1. 01Publish AI-generated HTML reports
  2. 02Share dashboard or document links
  3. 03Review documents in team spaces

MCP support

As a local MCP server, it provides Claude Code and Codex with tools to publish files, list spaces, and list documents, uploading HTML through the StelaSpace API.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "stelaspace-stelaspace": {
      "command": "npx",
      "args": [
        "-y",
        "stelaspace-mcp"
      ],
      "env": {
        "STELASPACE_API_KEY": "<STELASPACE_API_KEY>"
      }
    }
  }
}
Run commandnpx -y stelaspace-mcp
Environment variables to set
STELASPACE_API_KEYSecretStelaSpace API key (starts with ss_sk_) — create one at stelaspace.com under Settings → API Keys

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmstelaspace-mcp1.0.3

Tools

3

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
pathstringYesPath to the .html/.htm file on this machine (absolute, or relative to the MCP server's working directory).
slugstringNoDocument slug. Reuse an existing slug to publish a new version; omit to auto-generate.
tagsarrayNoOptional tags for organization and search.
titlestringNoDocument title. Defaults to the HTML <title> tag.
spaceSlugstringYesSlug of the target space — call list_spaces to find valid slugs.
visibilityenumNopublic = anyone with the link; private = team members only. Defaults to private.public | private

Details

From the project 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
claude mcp add stelaspace --scope user \
  --env STELASPACE_API_KEY=ss_sk_your_key \
  -- npx -y stelaspace-mcp
Codex

~/.codex/config.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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.