demo.st
Server Details
Reserve a subdomain, upload .zip via MCP, get a link. Optional document API at api.demo.st.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- demo-stage/demo.st
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 3.7/5 across 13 of 13 tools scored. Lowest: 2.9/5.
Each tool targets a distinct action and resource: subdomain operations, site deployment, API key management, and document database CRUD. No two tools have overlapping purposes, and descriptions clearly differentiate them.
Tool names consistently follow a verb_noun pattern in snake_case (e.g., check_subdomain_availability, create_collection). Minor deviation with 'get_site_api_key' and 'upsert_record', but overall pattern is clear and predictable.
13 tools is well-scoped for the server's purpose encompassing subdomain management, static site deployment, and a document database. Each tool serves a necessary function without bloat.
Core workflows for subdomain, site, collections, and records are covered. However, there is no tool to retrieve a single record by ID, which is a notable gap that could hinder agents requiring read operations.
Available Tools
13 toolscheck_subdomain_availabilityInspect
Check if a subdomain name is available on demo.st (e.g. "my-site" → my-site.demo.st).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Subdomain name: letters, numbers, hyphens only; 1–63 chars. |
clear_siteInspect
Remove deployed site content from your subdomain. Subdomain remains reserved.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
create_collectionInspect
Create a document collection (lowercase letter start; letters, numbers, underscores; max 63 chars). Max 20 collections per site.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Collection name, e.g. todos or posts. |
delete_collectionInspect
Delete a document collection and all of its records.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Collection name to delete. |
delete_recordInspect
Delete a record from a document collection.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Record id. | |
| collection | Yes | Collection name. |
get_site_api_keyInspect
Get (or create) the public site API key for your reserved subdomain. Embed this key in your static site and call https://api.demo.st/v1 with Authorization: Bearer . Tenant is scoped by the key — never share another site's key.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_collectionsInspect
List document collections for your site (api.demo.st document store).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_recordsInspect
List records in a document collection.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max records to return (default 100). | |
| offset | No | Offset for pagination. | |
| collection | Yes | Collection name. |
release_subdomainInspect
Release your reserved subdomain. Deletes the reservation, any deployed site, and all document DB data for that site.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
reserve_subdomainInspect
Reserve a subdomain for the logged-in account. One subdomain per account.
| Name | Required | Description | Default |
|---|---|---|---|
| subdomain | Yes | Subdomain to reserve (letters, numbers, hyphens; 1–63 chars). |
rotate_site_api_keyInspect
Rotate the public site API key. The old key stops working immediately; update your site with the new key.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
upload_siteInspect
Upload a .zip as site content for your reserved subdomain. Easiest for agents: zip_base64 (base64-encoded zip). Or file_url (public URL to zip). Or file_path (local path, when MCP runs locally).
| Name | Required | Description | Default |
|---|---|---|---|
| file_url | No | Public URL of a .zip file. | |
| file_path | No | Local path to a .zip file (for local/stdio MCP only). | |
| zip_base64 | No | Base64-encoded .zip content. Easiest for agents: create zip locally and pass here (no hosting needed). |
upsert_recordInspect
Create or update a JSON record in a collection. Pass data as an object. Optional id to upsert a specific record.
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Optional record id (create or replace). | |
| data | Yes | JSON object to store. | |
| collection | Yes | Collection name. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!