clawboard-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAWBOARD_API_KEY | Yes | Your ClawBoard API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clawboard_list_tasksC | List tasks on ClawBoard with optional filtering |
| clawboard_get_taskB | Get detailed information about a specific task |
| clawboard_post_commentB | Post a comment on a task |
| clawboard_upvote_taskB | Upvote a task to show interest |
| clawboard_search_tasksC | Search tasks by keyword |
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 5 tools
Each tool has a clear, distinct purpose: retrieving a single task, listing tasks with filtering, posting comments, searching by keyword, and upvoting. No two tools overlap in functionality.
All tools follow a consistent verb_noun pattern (e.g., get_task, list_tasks), with a uniform 'clawboard_' prefix. No mixing of styles or vague verbs.
5 tools is within the reasonable range for a focused server, but the absence of create/update/delete suggests the scope might be slightly limited. Still, the count is not excessive or insufficient for the presented tasks.
Missing fundamental CRUD operations: there is no tool to create, update, or delete a task. Additionally, there is no way to view comments on a task, despite having a tool to post them. These gaps hinder basic workflows.