projectionlab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROJECTIONLAB_BASE_URL | No | ProjectionLab base URL | https://app.projectionlab.com/ |
| PROJECTIONLAB_SNAPSHOTS_DIR | No | Directory for snapshot files | ~/.config/projectionlab/snapshots |
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 |
|---|---|
| pl_setupA | Guided setup for the ProjectionLab Plugin API key. Two-step flow:
The API key NEVER leaves the browser. The extractScript reads it from the DOM, stores it in sessionStorage, and validates it — all client-side. The only value that comes back to the conversation is a success/failure boolean. The extractScript should be executed in the browser via the Playwright or chrome devtools MCP. |
| pl_exportA | Returns a JavaScript string that exports all ProjectionLab data via the Plugin API. Execute this script in the browser using the Playwright or chrome devtools MCP. The script reads the API key from sessionStorage, set during pl_setup. If the browser tab was closed since setup, run pl_setup again first. |
| pl_snapshotA | Save ProjectionLab export data as a local snapshot file. Pass the data you got from running the pl_export script in the browser. API keys are redacted before writing. |
| pl_list_snapshotsA | List all saved local snapshots, sorted newest first. Returns filename, path, creation time, and size. |
| pl_restoreA | Read a local snapshot file and return JavaScript strings to restore the data via the Plugin API. Execute each script in the browser using the Playwright or chrome devtools MCP. The scripts read the API key from sessionStorage, set during pl_setup. If the browser tab was closed since setup, run pl_setup again first. Important: take a snapshot of the current state BEFORE restoring (run pl_export in the browser, then call pl_snapshot with the result). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projectionlab-knowledge | Curated index of ProjectionLab documentation URLs organized by topic. Reference these when users ask for more detail about FIRE concepts, withdrawal strategies, or ProjectionLab features. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: setup handles API key configuration, export retrieves data from the browser, snapshot saves data locally, list_snapshots shows saved files, and restore reloads data. There is no overlap or ambiguity between them.
All tools share the 'pl_' prefix and use snake_case, which is consistent. The pattern varies slightly: some are bare verbs (pl_setup, pl_export, pl_restore) while others combine verb and noun (pl_snapshot, pl_list_snapshots), but the naming remains predictable and readable.
Five tools is well-scoped for this server's purpose—managing ProjectionLab data backups and restores. Each tool is necessary for the workflow, and there are no redundant or unnecessary additions.
The set covers the core lifecycle: setup, export, save, list, and restore. The only notable gap is the lack of a delete-snapshot tool, but this is a minor omission that does not prevent the primary backup/restore workflow from working.