ws-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_workspacesB | List all workspaces with their metadata. Optionally filter by status or staleness. |
| get_workspaceA | Get detailed status of a specific workspace including git status, saved tabs, tab history summary, notes, and staleness. |
| get_workspace_treeA | Get the full workspace hierarchy as a tree structure. Shows parent-child relationships between workspaces. |
| find_stale_workspacesA | Find workspaces that have not been opened recently. Useful for identifying abandoned or forgotten projects. |
| search_workspacesA | Search across all workspace metadata, notes, and tab history for a query string. Searches workspace names, tags, workspace.md content, and saved tab titles/URLs. |
| summarize_allA | Get a high-level summary of all workspaces: counts by status, stale projects, recent activity. Designed for asking "where do things stand across all my projects?" |
| list_beadsA | List tasks from a workspace's beads issue tracker. Supports filtering by status, priority, type, and label. Returns tasks sorted by priority then creation date. |
| get_beads_across_workspacesA | Aggregate beads task counts across multiple workspaces. Shows per-workspace breakdown and totals. Scope to a parent prefix (e.g. "ws" for ws/* workspaces) or omit for all. |
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 8 tools
Most tools have clear, distinct purposes, but list_workspaces (with staleness filter) overlaps with find_stale_workspaces, and summarize_all also reports stale counts, causing potential confusion. The descriptions help differentiate, but an agent might misselect between these related tools.
All names are lowercase with underscores, but verbs vary (list, get, find, summarize, search). The verbs are semantically appropriate for each action, so the pattern is intuitive, though not as uniform as a pure verb_noun convention.
8 tools is well within the ideal 3-15 range for a workspace management server. Each tool covers a distinct aspect of workspace queries and bead aggregation without unnecessary bloat.
The tool set provides thorough read/query coverage for workspaces and bead tasks, including listing, details, hierarchy, staleness, search, and summaries. However, it lacks any mutation tools (create/update/delete) for workspaces or tasks, which may be a minor gap depending on the intended read-only scope.