serve-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVE_MCP_HOST | No | Host address to bind the HTTP shelf. Default: 127.0.0.1 | 127.0.0.1 |
| SERVE_MCP_PORT | No | Port to bind the HTTP shelf. Default: 7331 | 7331 |
| SERVE_MCP_DATA_DIR | No | Directory for the SQLite registry and snapshots. Default: ~/.local/share/serve-mcp | ~/.local/share/serve-mcp |
| SERVE_MCP_ALLOWED_ROOTS | No | Colon-separated list of allowed root directories for path/folder publishing. Default: anywhere readable |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| artifact_publishA | Publish a file, folder, or inline content to the local artifact shelf and get a stable browser preview URL back. Call this whenever you produce something viewable — a report, HTML page, diagram, dataset — so the user gets a URL without having to ask. Use the same slug with updateExisting:true to push new revisions of the same page. path/folder sources are read from the machine running the shelf; over remote MCP connections use content sources. |
| artifact_listB | List published artifacts on the shelf, newest first. Returns preview URLs humans can open. |
| artifact_deleteA | Remove a publication and ALL of its revisions from the shelf, including stored files. Irreversible. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| publications | All publications on the shelf as JSON |
TDQS
Scored across 3 tools
Each tool targets a distinct action: publish, list, or delete artifacts. There is no overlap in purpose, making it clear which tool to use for each operation.
All tools follow the consistent 'artifact_verb' pattern in snake_case, making the naming predictable and easy to navigate.
With only 3 tools, the server is well-scoped for its purpose: publishing, listing, and deleting artifacts. This is a focused set without unnecessary clutter.
The set covers core CRUD operations: create/update via artifact_publish, read via artifact_list, and delete via artifact_delete. A minor gap is the lack of a dedicated tool to retrieve a single artifact's details beyond the list.