askboard-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASKBOARD_PORT | No | Starting port for the local web server. If busy, Askboard probes the next ports. | 7717 |
| ASKBOARD_DATA_DIR | No | Directory for sessions.json. | ~/.askboard-mcp |
| ASKBOARD_TIMEOUT_MS | No | How long ask_user waits for a browser submission. | 600000 |
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 |
|---|---|
| ask_userA | Show the user an interactive web form (opens in their browser) to collect answers, instead of asking one question at a time in chat. Pass a list of questions; each can be single-choice, multi-choice, or free text, and can allow a custom write-in. The call blocks until the user submits, then returns their structured answers. Use this whenever you have a task list, a review checklist, or several questions for the user to decide on at once. |
| open_dashboardA | Open the local dashboard in the user's browser, where they can review every form that was shown before, what they submitted, and which choices they made. |
| get_updatesA | Incrementally read history. Pass the |
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 3 tools
Each tool has a clearly distinct purpose: ask_user collects answers via forms, open_dashboard presents a visual history, and get_updates provides programmatic incremental access to changes. No overlap or ambiguity exists between them.
All three tools follow a consistent verb_noun pattern with lowercase and underscores: ask_user, open_dashboard, get_updates. The naming is uniform and predictable.
Three tools is well-scoped for the server's purpose: asking questions, reviewing via dashboard, and syncing updates. Each earns its place without unnecessary bloat or missing essentials.
The tool set covers the full lifecycle of an askboard session: collecting responses via forms, reviewing all past submissions in the dashboard, and tracking edits through incremental updates. There are no obvious dead ends or missing core operations.