get_group_members
グループのメンバー一覧を取得する
LABSCO SUMMARY
Directory reads and three levels of notification, on client-credential headers.
The notification tools are the reason to wire it up: one call reaches the whole organization, a workspace filtered by permission level, or a single group — which is enough to route an alert from an automation to exactly the people who should see it. Everything else is directory lookup: workspaces, groups, members, and the URL that gets someone into a workspace. Install is from the GitHub repository rather than a registry, and the author is explicit that this is an unofficial personal project.
What it is
An unofficial server over the oVice Public API v1, covering the directory side of an organization and the notification endpoints. Its author describes it as a personal experiment with no guarantee of operation.
What you get
- The organization's workspaces listed, and the users in one of them
- The organization's groups listed, and the members of one group
- A space's name resolved from its ID
- The access URL for a workspace, built from the workspace information the API returns
- A notification sent to the whole organization, with a service name and logo you can override per call
- A notification sent to one workspace, targeted at the permission levels you name — admin, member, visitor or guest
- A notification sent to a single group
Requirements
oVice API credentials: OVICE_CLIENT_ID, OVICE_CLIENT_SECRET and OVICE_ORGANIZATION_ID are all required, and the client id and secret are sent as headers on every call. OVICE_DOMAIN defaults to api.ovice.com and needs changing for non-production environments. OVICE_SERVICE_NAME and OVICE_SERVICE_LOGO_URL set the branding that appears on notifications. It is run straight from the repository — npx github:cti1650/ovice-mcp-server — rather than from a published npm package. Calls go to https://{OVICE_DOMAIN}/api/public/v1/. Tool descriptions are in Japanese.
Setup effort
One command plus credentials — npx github:cti1650/ovice-mcp-server, then supply credentials
USE CASES
01
Telling the whole organization something happened
Send the notification with your own service name and logo on it.
02
Alerting only the admins of one workspace
Find the workspace, then send the notification targeted at that permission level.
03
Reaching one team without messaging everyone
List the groups, check who is in the right one, and send to that group.
04
Handing someone the link to join a workspace
Generate the access URL for that workspace from its ID.
05
Working out who is in a workspace
List its users, and resolve any space IDs you have into readable names.
9 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_organization_groups
組織のグループ一覧を取得する
get_organization_workspaces
組織のワークスペース一覧を取得する
get_space_name_by_id
スペースIDからスペース名を取得する
get_workspace_access_path
ワークスペースにアクセスするためのパスを返す
get_workspace_users
ワークスペースのユーザー一覧を取得する
send_group_notification
グループに通知を送信する
send_organization_notification
組織に通知を送信する
send_workspace_notification
ワークスペースに通知を送信する
BEFORE YOU INSTALL
What to know first
Tools you get
9 tools when we connected. send_organization_notification reaches everyone in the organization, and send_workspace_notification can target admins, members, visitors or guests. The documentation is in Japanese only.
Requires
- npx on PATH
- OVICE_CLIENT_ID in your environment
- OVICE_CLIENT_SECRET in your environment
- OVICE_ORGANIZATION_ID in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx github:cti1650/ovice-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"ovice-mcp-server": {
"command": "npx",
"args": [
"github:cti1650/ovice-mcp-server"
],
"env": {
"OVICE_DOMAIN": "api.ovice.com",
"OVICE_CLIENT_ID": "<YOUR_OVICE_CLIENT_ID>",
"OVICE_CLIENT_SECRET": "<YOUR_OVICE_CLIENT_SECRET>",
"OVICE_ORGANIZATION_ID": "<YOUR_OVICE_ORGANIZATION_ID>",
"OVICE_SERVICE_NAME": "<YOUR_OVICE_SERVICE_NAME>",
"OVICE_SERVICE_LOGO_URL": "<YOUR_LOGO_URL>/logo.svg"
}
}
}
}
