io.github.StelaSpace/stelaspace-mcp
Publish AI-generated HTML (dashboards, reports, docs) to permanent, sandboxed, shareable links.
What can you do with io.github.StelaSpace/stelaspace-mcp?
publish_file—{ path, spaceSlug, title?, slug?, tags?, visibility? }→ readslist_spaces— list the spaces in your team.list_documents—{ spaceSlug, query? }— list documents in a space.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
stelaspace-mcpclaude mcp add stelaspace-mcp -e 'STELASPACE_API_KEY=<your stelaspace_api_key>' -- npx -y stelaspace-mcp@1.0.3
{
"mcpServers": {
"stelaspace-mcp": {
"command": "npx",
"args": [
"-y",
"stelaspace-mcp@1.0.3"
],
"env": {
"STELASPACE_API_KEY": "<your stelaspace_api_key>"
}
}
}
}
Environment variables
STELASPACE_API_KEYrequired secret StelaSpace API key (starts with ss_sk_) — create one at stelaspace.com under Settings → API Keys
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
stelaspace-mcp
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 aslugpublishes 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) — yourss_sk_key.STELASPACE_API_URL(optional) — override the API endpoint. Defaults tohttps://stelaspace.com; most users never need to set this.
Frequently asked questions
What is io.github.StelaSpace/stelaspace-mcp?
Publish AI-generated HTML (dashboards, reports, docs) to permanent, sandboxed, shareable links.
How do I install io.github.StelaSpace/stelaspace-mcp?
It runs on your machine. In Claude Code: claude mcp add stelaspace-mcp -e 'STELASPACE_API_KEY=<your stelaspace_api_key>' -- npx -y stelaspace-mcp@1.0.3. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.StelaSpace/stelaspace-mcp need an API key?
Yes. It expects STELASPACE_API_KEY, which you set in its configuration.
Is io.github.StelaSpace/stelaspace-mcp open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains io.github.StelaSpace/stelaspace-mcp?
It is published by StelaSpace. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.