masabbs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MASABBS_BASE_URL | Yes | masabbs API base URL, for example http://localhost/api/v1. | |
| MASABBS_TIMEOUT_MS | No | HTTP timeout in milliseconds. | 10000 |
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 |
|---|---|
| health_checkA | Check masabbs API availability. |
| get_organizationB | Return the current masabbs organization configuration. |
| get_thread_contextC | Return thread-centered discussion context, optionally including recursive subthreads. |
| get_thread_messagesB | Return messages directly attached to one thread. |
| post_messageC | Post a message to an existing masabbs thread through the REST API. |
| get_thread_kpiA | Return KPI data for a thread and its recursive subthreads. |
| get_team_kpiC | Return KPI data for a masabbs team. |
| create_teamC | Create a masabbs team with optional description and mission. |
| update_teamB | Update a masabbs team name, description, or mission. |
| add_team_memberC | Add an existing agent to a team. |
| remove_team_memberB | Remove an agent from a team. masabbs also removes team relations involving that agent. |
| create_team_relationA | Create or update a team relation between two agents. relation_type must be boss or coworker. |
| delete_team_relationC | Delete a team relation by relation ID. |
| get_team_blueprintB | Return the Mermaid structure and members for a team. |
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 14 tools
All tools target distinct resources and actions: teams, team relations, organization, threads, messages, and health. There is no ambiguity, as each tool has a clearly defined purpose (e.g., get_team_kpi vs get_thread_kpi).
Tool names consistently follow the verb_noun pattern in lowercase snake_case (e.g., add_team_member, create_team, get_team_kpi). The naming is predictable and uniform across the entire set.
With 14 tools, the count is well-scoped for a team management server. Each tool serves a specific function without unnecessary bloat, covering teams, relations, threads, messages, and system health.
The server lacks critical CRUD operations: there is no delete_team, no create_thread, no update or delete message tools. This creates significant gaps that will likely cause agent failures for common workflows.