@lastbluetape/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LASTBLUETAPE_API_KEY | Yes | Your API key (`lbt_xxx`) | |
| LASTBLUETAPE_BASE_URL | No | API base URL (default: `https://lastbluetape.com`) | |
| LASTBLUETAPE_PAYMENT_METHOD | No | Stripe payment method ID (`pm_xxx`) for auto-upgrading lists |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_listA | Create a new punch list. Returns the list details, share token, and a shareable web URL. |
| list_my_listsA | List all punch lists linked to your API key. Also refreshes the token cache for list-level operations. |
| get_listA | Get details and stats for a specific punch list. |
| list_itemsB | List all items in a punch list. |
| add_itemA | Add a new item to a punch list. Returns the created item and list stats (including remaining capacity for free lists). |
| update_itemB | Update the title and/or description of a punch list item. |
| set_item_statusB | Change the status of a punch list item to open, in_progress, or done. |
| flag_itemB | Flag or unflag a punch list item for attention. |
| get_activityA | Get the activity log for a punch list. |
| upgrade_listA | Upgrade a punch list to Pro ($4.99 one-time). Requires LASTBLUETAPE_PAYMENT_METHOD env var with a Stripe payment method ID. Removes the 30-item limit and 90-day expiry. |
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 10 tools
Each tool targets a distinct resource and action: list, item, activity, upgrade. There is no overlap in purpose; an agent can clearly distinguish between creating a list, getting a list, listing items, adding items, updating items, changing status, flagging, viewing activity, and upgrading. No ambiguity.
All tool names follow a consistent verb_noun pattern (e.g., create_list, list_items, set_item_status, upgrade_list). The verb is always placed first and is descriptive of the action, making the set predictable and easy to navigate for an agent.
With 10 tools, the server is well-scoped for a punch list management system. Each tool addresses a core operation without bloat, covering list creation, retrieval, item management, status changes, flagging, activity logging, and upgrade. The count feels complete yet focused.
The tool surface covers most common operations for a punch list, but notable gaps exist: there is no tool to delete a list or delete an item, and no way to update list metadata (e.g., name, description). These missing delete and update operations could leave agents unable to complete certain workflows, such as removing outdated entries.