StelaSpace
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STELASPACE_API_KEY | Yes | Your StelaSpace API key (starts with ss_sk_) | |
| STELASPACE_API_URL | No | Override the API endpoint | https://stelaspace.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| publish_fileA | Upload a local .html/.htm file to a StelaSpace space and get back a permanent, shareable URL. The file is read from disk by path, so large files work fine. Reusing a slug publishes a new version. |
| list_spacesA | List the spaces in your team. Use a space's slug as the spaceSlug when publishing a document. |
| list_documentsA | List documents in a space, optionally filtered by a case-insensitive title search term. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: listing documents, listing spaces, and publishing files. There is no overlap between their functionalities.
All tool names follow a consistent verb_noun pattern: list_documents, list_spaces, and publish_file. The naming is clear and predictable.
With 3 tools, the server is well-scoped for a simple document publishing service. The count falls within the ideal 3-15 range, and each tool serves a clear role.
The tool set covers listing and publishing but lacks essential operations like deleting documents or retrieving a single document's details. These gaps could hinder common workflows.