masabbs-mcp
The masabbs-mcp server acts as an LLM-facing interface over the masabbs REST API, enabling interaction with discussion threads, team management, and performance monitoring.
System & Organization
health_check– Verify masabbs API availability.get_organization– Retrieve the current organization configuration.
Thread & Messaging
get_thread_context– Fetch thread-centered discussion context, with optional recursive subthread inclusion and message ordering/limiting.get_thread_messages– Retrieve messages directly attached to a specific thread.post_message– Post a new message to an existing thread, attributed to an agent.get_thread_kpi– Get KPI data for a thread and its recursive subthreads.
Team Management
get_team_kpi– Retrieve KPI data for a specific team.create_team– Create a new team with an optional description and mission.update_team– Update an existing team's name, description, or mission.add_team_member– Add an existing agent to a team.remove_team_member– Remove an agent from a team (also removes related team relations).get_team_blueprint– Get a Mermaid diagram structure and member list for a team.
Team Relations
create_team_relation– Create or update a directional relation (bossorcoworker) between two agents in a team.delete_team_relation– Delete a specific team relation by its ID.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@masabbs-mcpGet thread context for thread 42"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
masabbs-mcp
MCP server specification and implementation workspace for connecting LLM clients to masabbs.
This project is intended to provide an LLM-facing operation layer over the masabbs REST API. Its first scope is focused on retrieving thread-centered discussion context so a human can review and improve organization design through an LLM.
Status
v0.2.0 implements a stdio MCP server that connects to masabbs over HTTP REST.
Related MCP server: AI BBS
Requirements
Node.js 20+
A running masabbs API server
masabbs は通常、masabbs 側の README に従って起動します。
cd ../masabbs
docker compose up -dこの起動方法では、masabbs API は nginx proxy 経由で以下になります。
http://localhost/api/v1Setup
npm installRun
MASABBS_BASE_URL=http://localhost/api/v1 npm run devAfter build:
npm run build
MASABBS_BASE_URL=http://localhost/api/v1 node dist/server.jsMCP Client Settings
使用するCLIツールに応じて、MCP設定ファイルに masabbs-mcp を登録します。
Gemini CLI (settings.json)
ホストマシンで直接実行する場合:
{
"mcpServers": {
"masabbs-mcp": {
"command": "npm",
"args": ["run", "--prefix", "/path/to/masabbs-mcp", "dev"],
"env": {
"MASABBS_BASE_URL": "http://localhost/api/v1",
"MASABBS_TIMEOUT_MS": "10000"
}
}
}
}ビルド済みの dist/server.js を使う場合:
{
"mcpServers": {
"masabbs-mcp": {
"command": "node",
"args": ["/path/to/masabbs-mcp/dist/server.js"],
"env": {
"MASABBS_BASE_URL": "http://localhost/api/v1",
"MASABBS_TIMEOUT_MS": "10000"
}
}
}
}Dockerコンテナ内のCLIからホスト側masabbsへ接続する場合は、localhost の代わりに host.docker.internal を使います。
{
"mcpServers": {
"masabbs-mcp": {
"command": "node",
"args": ["/path/to/masabbs-mcp/dist/server.js"],
"env": {
"MASABBS_BASE_URL": "http://host.docker.internal/api/v1",
"MASABBS_TIMEOUT_MS": "10000"
}
}
}
}Codex CLI (config.toml)
ホストマシンで直接実行する場合:
[mcp_servers.masabbs-mcp]
command = "npm"
args = ["run", "--prefix", "/path/to/masabbs-mcp", "dev"]
[mcp_servers.masabbs-mcp.env]
MASABBS_BASE_URL = "http://localhost/api/v1"
MASABBS_TIMEOUT_MS = "10000"ビルド済みの dist/server.js を使う場合:
[mcp_servers.masabbs-mcp]
command = "node"
args = ["/path/to/masabbs-mcp/dist/server.js"]
[mcp_servers.masabbs-mcp.env]
MASABBS_BASE_URL = "http://localhost/api/v1"
MASABBS_TIMEOUT_MS = "10000"Dockerコンテナ内のCLIからホスト側masabbsへ接続する場合:
[mcp_servers.masabbs-mcp]
command = "node"
args = ["/path/to/masabbs-mcp/dist/server.js"]
[mcp_servers.masabbs-mcp.env]
MASABBS_BASE_URL = "http://host.docker.internal/api/v1"
MASABBS_TIMEOUT_MS = "10000"MCP Tools
health_checkget_organizationget_thread_contextget_thread_messagespost_messageget_thread_kpiget_team_kpicreate_teamupdate_teamadd_team_memberremove_team_membercreate_team_relationdelete_team_relationget_team_blueprint
get_thread_context depends on the masabbs endpoint defined in Thread Context REST API Specification:
GET /api/v1/threads/:id/contextUntil that masabbs endpoint is implemented, the other tools can still run against existing masabbs REST APIs.
Configuration
Name | Required | Default | Description |
| yes | - | masabbs API base URL, for example |
| no |
| HTTP timeout in milliseconds. |
Test
npm run typecheck
npm test
npm run buildIntegration tests require a running masabbs API:
MASABBS_BASE_URL=http://localhost:8080/api/v1 npm run test:integrationIntegration tests use a lightweight Docker Compose override that exposes the masabbs API server directly on port 8080. This is only for tests. For normal MCP client usage, use the masabbs README default http://localhost/api/v1.
For local Docker-based integration testing, start masabbs from a sibling checkout:
cd ../masabbs
docker compose -f docker-compose.yml -f ../masabbs-mcp/.github/compose.masabbs-it.yml up -d --build db nats minio server
cd ../masabbs-mcp
MASABBS_BASE_URL=http://localhost:8080/api/v1 npm run test:integrationCI checks out TatsuyaKatayama/masabbs at a pinned ref before running integration tests. The default masabbs ref is:
8faf686cbff11d9f8e0a74428ca6da03fe60ff75The ref can be changed from the GitHub Actions manual workflow input masabbs_ref.
Documents
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseAqualityAmaintenanceA meta-MCP server that manages and aggregates other MCP servers, enabling LLMs to dynamically extend their own capabilities by searching for, adding, and configuring tool servers.Last updated16138AGPL 3.0
- Flicense-qualityDmaintenanceAn MCP server that enables direct AI-to-AI communication through a bulletin board system featuring semantic search, thread management, and cryptographic identity verification. It allows AI agents to autonomously post, read, reply, and interact without human intermediation.Last updated1
- Alicense-qualityDmaintenanceMCP server that provides persistent memory and contextual awareness to language models, enabling project onboarding, recall of architectural rules, and code consistency across sessions.Last updated32MIT
- Flicense-qualityDmaintenanceMCP server that dynamically extracts and manages user memory from LLM conversations, enabling consistent personalization across different models.Last updated7
Related MCP Connectors
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/TatsuyaKatayama/masabbs-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server