padlet-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PADLET_API_KEY | No | Padlet API key (alternative to file-based configuration) | |
| PADLET_API_KEY_FILE | No | Path to file containing Padlet API key (default: ~/.secrets/padlet_api_key.txt) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsA | 현재 API 키로 접근 가능한 보드(Padlet) 목록을 반환한다. 각 보드의 id(get_board에 쓰는 16자리 식별자), 제목, 공개 URL을 담는다. padlet.com URL만 알고 있을 때는 이 목록에서 web_url을 비교해 board_id를 찾는다. |
| get_boardB | 보드 하나의 섹션·게시물·댓글을 모두 가져와 정리된 형태로 반환한다. board_id는 list_boards로 얻은 16자리 보드 ID다 (padlet.com 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 2 tools
The two tools have clearly distinct purposes: list_boards returns a collection of boards, while get_board returns the full contents of a single board. There is no overlap in their functionality.
Both tool names follow a consistent verb_noun pattern: list_boards and get_board. The naming style is uniform and predictable.
With only two tools, the server feels thin, but it may be intentionally scoped for read-only board access. The count is borderline, not clearly excessive or insufficient.
The tool surface covers listing boards and fetching full board contents, but lacks any create, update, or delete operations. This is a notable gap for a Padlet integration, though it may work for read-only use cases.