Ovice MCP Server

このMCPサーバーは [oVice Public API v1](https://help.ovice.com/hc/ja/articles/27613800985753-%E3%83%91%E3%83%96%E3%83%AA%E3%83%83%E3%82%AFAPI) を使用します: -

Local serverstdio

What is the Ovice MCP server?

Connect Ovice to Claude, Cursor or any other MCP client and it stops being a tab you switch to. このMCPサーバーは oVice Public API v1 を使用します: - エンドポイント: https://{OVICE_DOMAIN}/api/public/v1/ - 認証: クライアントIDとクライアントシークレットによるヘッダー認証. The ovice mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • get_organization_workspaces — The get_organization_workspaces tool exposed by this server
  • get_workspace_users — The get_workspace_users tool exposed by this server
  • get_space_name_by_id — The get_space_name_by_id tool exposed by this server
  • get_workspace_access_path — The get_workspace_access_path tool exposed by this server
  • get_organization_groups — The get_organization_groups tool exposed by this server
  • get_group_members — The get_group_members tool exposed by this server
  • send_organization_notification — The send_organization_notification tool exposed by this server
  • send_workspace_notification — The send_workspace_notification tool exposed by this server
  • send_group_notification — The send_group_notification tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: OVICE_DOMAIN, OVICE_CLIENT_ID, OVICE_CLIENT_SECRET, OVICE_ORGANIZATION_ID, OVICE_SERVICE_NAME, OVICE_SERVICE_LOGO_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ovice's toolset — get_organization_workspaces, get_workspace_users, get_space_name_by_id and 6 more — is a fair guide to whether it matches your workflow. It is maintained by cti1650; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ovice.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
get_organization_workspacesThe get_organization_workspaces tool exposed by this server.
get_workspace_usersThe get_workspace_users tool exposed by this server.
get_space_name_by_idThe get_space_name_by_id tool exposed by this server.
get_workspace_access_pathThe get_workspace_access_path tool exposed by this server.
get_organization_groupsThe get_organization_groups tool exposed by this server.
get_group_membersThe get_group_members tool exposed by this server.
send_organization_notificationThe send_organization_notification tool exposed by this server.
send_workspace_notificationThe send_workspace_notification tool exposed by this server.
send_group_notificationThe send_group_notification tool exposed by this server.

How to install the Ovice MCP server

{
  "mcpServers": {
    "ovice-mcp-server": {
      "command": "npx",
      "args": ["github:cti1650/ovice-mcp-server"],
      "env": {
        "OVICE_DOMAIN": "api.ovice.com",
        "OVICE_CLIENT_ID": "your-client-id",
        "OVICE_CLIENT_SECRET": "your-client-secret",
        "OVICE_ORGANIZATION_ID": "your-organization-id",
        "OVICE_SERVICE_NAME": "Your Service Name",
        "OVICE_SERVICE_LOGO_URL": "https://your-logo-url.com/logo.svg"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
OVICE_DOMAINConfiguration value read at startup.Optional
OVICE_CLIENT_IDConfiguration value read at startup.Optional
OVICE_CLIENT_SECRETCredential the server authenticates with.Yes
OVICE_ORGANIZATION_IDConfiguration value read at startup.Optional
OVICE_SERVICE_NAMEConfiguration value read at startup.Optional
OVICE_SERVICE_LOGO_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Ovice to get organization workspaces.
  • Use Ovice to get workspace users.
  • Use Ovice to get space name by id.

Frequently asked questions

It connects Ovice to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (get_organization_workspaces, get_workspace_users, get_space_name_by_id, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ovice directly.