plaky-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAKY_API_KEY | Yes | Plaky API key, sent as X-API-Key. | |
| PLAKY_BASE_URL | No | Override the API base URL. | https://api.plaky.com |
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 |
|---|---|
| plaky_get_current_userA | Get the user that owns the API key making the request. Useful for verifying authentication and discovering the caller's user id. |
| plaky_list_usersA | List users in the workspace. Optionally filter by emails, status, or membership type. Supports pagination. |
| plaky_list_teamsB | List all teams in the workspace. Supports pagination. |
| plaky_get_teamB | Get a single team by its id. |
| plaky_list_spacesB | List spaces in the workspace. Spaces are top-level containers that hold boards. Use expand=["board"] to include full board objects. |
| plaky_get_spaceB | Get a single space by its id. |
| plaky_list_boardsA | List the boards contained in a given space. Supports pagination. |
| plaky_get_boardA | Get a single board by id, including its structure: groups, field/column definitions and their configurations (status labels, tag labels, etc.). Read this before creating or updating items so you know the available field keys/titles and allowed values. |
| plaky_list_itemsA | List items (rows) on a board, with optional filtering. Supports pagination; the response includes a |
| plaky_get_itemB | Get a single item by id, including its field values. |
| plaky_list_subitemsB | List the subitems nested under a given item. Supports pagination. |
| plaky_create_itemA | Create a new item (row) on a board, or a subitem when |
| plaky_delete_itemA | Permanently delete an item (and its subitems) by id. This cannot be undone. |
| plaky_update_item_fieldA | Change the value of one field on an item, identified by the field key or title ( |
| plaky_update_item_fieldsA | Change several field values on an item in one request. |
| plaky_list_item_commentsB | List all comments on an item, including replies and reaction details. |
| plaky_create_item_commentB | Add a comment to an item. Set |
| plaky_update_item_commentB | Edit the text of an existing comment. |
| plaky_delete_item_commentC | Permanently delete a comment by id. |
| plaky_set_comment_reactionsA | Set the authenticated user's reactions on a comment. This OVERRIDES any existing reactions by the caller; pass an empty array to remove all of them. Each reaction is an emoji's unicode codepoint without the "U+" prefix (case-insensitive) — e.g. "1f44d" (thumbs up), "2705" (check mark), "2764" (heart). |
| plaky_list_item_filesB | List the files attached to an item. |
| plaky_get_item_fileA | Get metadata for a single file attached to an item. |
| plaky_upload_item_fileA | Upload a local file and attach it to an item. Provide the absolute path to a file on the machine running this MCP server. |
| plaky_update_item_fileA | Rename a file or change its description. The original file extension/type is preserved regardless of the name given. |
| plaky_delete_item_fileB | Permanently delete a file attached to an item. |
| plaky_download_item_fileA | Download a file attached to an item. If the API returns JSON (e.g. a presigned download URL) that is returned directly. If it returns binary content, provide |
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 26 tools
Each tool targets a distinct resource-action combination (e.g., create_item vs. create_item_comment, update_item_field vs. update_item_fields). There is no ambiguity between tools; even similar ones like list_items and list_subitems are clearly differentiated by resource.
All tools follow the pattern 'plaky_<verb>_<noun>' in snake_case. Verbs are consistent (create, delete, get, list, update, etc.) and nouns correspond to the resource. No mixing of conventions.
26 tools is on the higher side but still appropriate for a comprehensive project management MCP server covering items, comments, files, boards, spaces, users, and teams. Each tool serves a distinct purpose; the count is justified by the domain's breadth.
The tool surface covers core CRUD operations for items, comments, and files, plus listing for boards, spaces, users, teams, and subitems. Missing operations like creating/updating boards or spaces are minor gaps for a tool focused on item-level management.