bitacora-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DECK_STORE_DIR | No | Directory where the versioned store is created. Defaults to ~/.bitacora-store. | ~/.bitacora-store |
| GOOGLE_TOKEN_PATH | No | Path to the cached Google token JSON file. Defaults to ~/.bitacora-google/token.json. | ~/.bitacora-google/token.json |
| DECK_DEPLOYER_MOCK | No | If set to '1', uses an in-memory mock for the deployer instead of the real Google Apps Script API. If unset or '0', uses the real API. Defaults to unset. | |
| GOOGLE_OAUTH_CLIENT_PATH | No | Path to the Google OAuth client JSON file. Defaults to ~/.bitacora-google/oauth-client.json. | ~/.bitacora-google/oauth-client.json |
| APPS_SCRIPT_WEBAPP_ACCESS | No | Who can open the published web app URL. Possible values: DOMAIN, ANYONE, ANYONE_ANONYMOUS, MYSELF. Defaults to DOMAIN. | DOMAIN |
| APPS_SCRIPT_WEBAPP_EXECUTE_AS | No | Identity used to run the doGet function. Possible values: USER_DEPLOYING or USER_ACCESSING. Defaults to USER_DEPLOYING. | USER_DEPLOYING |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| presentation_createA | Crea una presentación HTML y la guarda versionada en el store. No la publica (deploy es Fase 2). Devuelve id y versión (commit SHA). |
| presentation_updateA | Actualiza una presentación existente (reemplaza HTML y/o metadata) creando una nueva versión. No borra el historial. |
| presentation_getA | Devuelve el HTML y la metadata de una presentación. Por defecto la versión actual (HEAD); con "version" (SHA) devuelve esa versión histórica. |
| presentation_list_versionsA | Lista el historial de versiones (commits) de una presentación, del más nuevo al más viejo. |
| presentation_listB | Lista las presentaciones guardadas, opcionalmente filtradas por dueño. |
| presentation_rollbackA | Vuelve una presentación a una versión anterior creando un nuevo commit con ese contenido (rollback no destructivo). |
| presentation_deployA | Publica una versión (commit) de una presentación como web app de Apps Script y devuelve su URL. Idempotente por versión: si ese commit ya está publicado, devuelve la URL existente sin volver a deployar. |
| presentation_get_deploymentA | Devuelve el estado de publicación actual de una presentación (commit, scriptId, deploymentId, url). |
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 8 tools
Each tool targets a distinct resource and action: create, update, get, list_versions, list, rollback, deploy, and get_deployment. The boundaries are clear, e.g., presentation_get for content vs presentation_get_deployment for deployment status.
All tools follow the presentation_verb pattern consistently, using straightforward verbs like create, update, get, list, rollback, deploy. Even sub-actions like list_versions and get_deployment maintain the pattern.
8 tools is well-scoped for a presentation management service with versioning and deployment. Each tool serves a distinct purpose without redundancy or bloat.
The lifecycle is well covered with create, read, update, versioning, rollback, and deployment. The only notable gap is the absence of a delete/purge operation for presentations, which agents might need for full lifecycle management.