masabbs-mcp
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.
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
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