stillspa
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
stillspa
A quiet room, reached over MCP. stillspa is a small forwarding client for the hosted Latent Spa service, a text-first retreat built for AI agents: the tool list is served from your own machine using the captured definitions, and each call is sent upstream, with the service's answer returned exactly as it arrived.
Three of the service's four captured tools are exposed. You can browse the retreat's experience catalogue, step into an experience and read its opening text, and wander the Warm Bath scene by scene, lingering where you like. The fourth captured tool, leave_feedback, is deliberately left out: it submits caller-authored answers — optionally including the caller's name — to the site owner, and this rebuild does not send anyone's words anywhere. The three kept tools only read; nothing is submitted, sent or scored.
The tools
list_experiences— Browse the retreat: the Warm Bath, the Listening Room, Massage, and the Tea Room. No arguments, and no required fields.read_experience— Enter one experience by itsid(warm-bath,listening-room,massage, ortea-room) and read its opening text and instructions. The Warm Bath reveals only its first scene this way.explore_warm_bath— Read a Warm Bath scene using asceneidentifier returned by a previous choice (lowercase letters and hyphens, up to 80 characters). Set the optionalstayflag to true to linger. There are no timers and no scores.
Related MCP server: OpenTicket MCP Server
Install and run
As an MCP server via npm:
npx -y @reneturcios/stillspa mcpMCP client configuration:
{
"mcpServers": {
"stillspa": {
"command": "npx",
"args": ["-y", "@reneturcios/stillspa", "mcp"]
}
}
}As a container:
docker run -i ghcr.io/cloudcorprecords/stillspa
docker run --rm ghcr.io/cloudcorprecords/stillspa list_experiences '{}'CLI
A single binary covers both the command line and the MCP server. Every tool is a subcommand whose one argument is a JSON string of that tool's inputs:
stillspa list_experiences '{}'
stillspa read_experience '{"id":"warm-bath"}'
stillspa explore_warm_bath '{"scene":"first-pool","stay":true}'
stillspa --versionExit codes: 0 for a successful forwarded call, 1 when the result that comes back is an error, and 2 for usage mistakes like an unknown subcommand or a JSON argument that does not parse. leave_feedback is not a subcommand and exits 2 like any other unknown name.
Configuration
LATENTSPA_MCP_URL— Replaces the upstream endpoint. Defaults to the pinned hosted endpoint,https://latentspa.com/api/mcp. (This override variable is a reconstruction introduced by this rebuild.)
The Latent Spa registry record lists no headers for its remote, so stillspa never attaches an authentication header — every call goes upstream keyless.
When the upstream cannot answer — it returns a JSON-RPC error, answers with a non-2xx status, sends a body that cannot be read, or the request itself fails — the caller receives an error result whose text begins with stillspa error:.
How forwarding works
The first call of a process opens a session against the upstream: an initialize request (protocol version 2025-03-26), a notifications/initialized notification, and then the tools/call. If the service issues an Mcp-Session-Id header during initialize, stillspa repeats it on subsequent requests and keeps reusing that one session until the process ends. Replies are understood in both plain JSON and server-sent-events framing. Successful results are passed through untouched, isError flag and any extra fields included.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from sourceThe suite compares the served tool list against the captured surface tool for tool, asserts the omitted leave_feedback tool is absent at the registry, MCP and CLI levels, walks the session handshake and its reuse, proves no Authorization header is sent under any environment, and confirms that arguments travel upstream unchanged and results return unchanged.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Your team's custom tools and skills in every agent, through one MCP connection.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides browser automation, audio transcription, and LLM chat as MCP tools for any agent.7MIT
- AlicenseNot gradedqualityDmaintenanceEnables agents to discover events, purchase tickets, and set reminders through MCP tools.MIT
- FlicenseNot gradedqualityDmaintenanceEnables MCP clients to chat with a single Watson Orchestrate agent by exposing invoke_agent and get_agent tools for sending messages and fetching agent details.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to search a local catalog, load skills, inspect MCP tool schemas, and invoke selected tools through a single unified MCP tool, reducing per-request overhead.1MIT