garoon-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| https_proxy | No | HTTPSプロキシのURL（例: http://proxy.example.com:8080） | |
| GAROON_BASE_URL | Yes | Garoon環境のベースURL（例: https://example.cybozu.com/g） | |
| GAROON_PASSWORD | Yes | Garoonのログインパスワード | |
| GAROON_USERNAME | Yes | Garoonのログイン名 | |
| GAROON_PUBLIC_ONLY | No | 非公開予定を除外するモード（デフォルト: false） | |
| GAROON_PFX_FILE_PATH | No | クライアント証明書（*.pfx）の絶対パス | |
| GAROON_PFX_FILE_PASSWORD | No | クライアント証明書のパスワード | |
| GAROON_BASIC_AUTH_PASSWORD | No | Basic認証のパスワード | |
| GAROON_BASIC_AUTH_USERNAME | No | Basic認証のユーザー名 |
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 |
|---|---|
| garoon-create-schedule-eventA | Create a new schedule event in Garoon |
| garoon-get-schedule-eventsB | Search for schedule events in a specified period in Garoon |
| garoon-search-available-timesA | Search for available time slots for specified attendee or facility within given time ranges in Garoon |
| garoon-get-facilitiesA | Get facilities data from Garoon by searching facility names with optional limit and offset parameters. |
| garoon-get-facility-groupsB | Get facility groups data from Garoon with optional limit and offset parameters. |
| garoon-get-facilities-in-groupA | Get facilities that belong to a specific facility group with optional limit and offset parameters. |
| garoon-get-current-timeA | Get the current datetime in RFC 3339 format in Garoon. |
| garoon-get-usersA | Get user data (name, ID, code) from Garoon by searching name/code. IMPORTANT: Omit name parameter for self-referential queries ('me', 'my', 'I', 'myself', 私, 僕, 自分) to return current user info. Supports pagination. |
| garoon-get-organizationsA | Get Garoon organization's name, ID, and code data by searching for organization names - supports pagination with optional limit and offset parameters. |
| garoon-get-users-in-organizationA | Get users from a specific organization with support for pagination parameters (limit, offset) in Garoon. |
| garoon-get-bulletin-categoriesA | Get bulletin board categories from Garoon. Use parentId to browse sub-categories. Special values: 1=root (default), -1=pending approval, -2=drafts. |
| garoon-get-bulletin-topicsA | Get bulletin board topics in a specific category from Garoon. Returns topic summaries with subject, updater, and update time. |
| garoon-get-bulletin-topicA | Get full details of a specific bulletin board topic from Garoon, including body content, attachments, public period, and metadata. |
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 13 tools
Each tool targets a distinct resource-action combination: schedules, bulletin topics/categories, facilities/groups, users/organizations, and current time. Even 'get-schedule-events' and 'search-available-times' serve clearly separate purposes.
All tools follow the consistent `garoon-<verb>-<object>` pattern, with get, search, and create as the only verbs. The naming style is uniformly snake_case and easily predictable.
13 tools is a reasonable size for a Garoon integration, covering several major modules without feeling bloated. However, the inclusion of a simple current-time utility is slightly peripheral and pushes the count marginally higher than necessary.
The set covers read/search operations well across schedules, bulletin boards, facilities, users, and organizations, and it can create schedule events. However, it lacks obvious lifecycle operations like updating or canceling events, or creating updating, or deleting bulletin topics, leaving notable workflow gaps.