Skip to content

Plugins

Plugins are InHive-built integrations a manager installs from Organization settings → Plugins. There is no third-party marketplace and no sandbox for outside developers.

Three entries matter today:

PluginPlanJob
Monday.comEvery planOne-shot board import
Agents (MCP)Install is hive-level; use is Studio+ / TeamLets people connect Cursor / Claude
Google DriveTeamMirror a Drive folder into Documents

Migration is not an upsell.

  1. Organization settings → Plugins → Monday → connect (hive-wide OAuth).
  2. Start the wizard. Map people first (map to existing users, invite, or skip).
  3. Pick boards and tell InHive what each column means (status, assignee, due date, …).
  4. Preview, then run. Imported boards become projects.

You can skip items that already came across. This is a one-shot move, not a live two-way sync. Changing Monday later does not update InHive.

If people are skipped, their cards arrive unassigned. Map them on a second thought, or assign in InHive.

  1. Install and connect hive-wide OAuth (managers).
  2. On a project, attach a Drive folder (shared tree, and optionally a budget folder).
  3. Sync. Files land in Documents and follow the same visibility and ingest rules as uploads.

The budget / managers folder is not ingested. Disconnecting stops the mirror; it does not delete what already arrived.

The Plugins card installs Agents for the hive and sets the write-mode ceiling (confirm only, or allow members to choose auto). Each person then connects with their own token under Account → Agents. There is no shared hive credential.

See Agents for install, PAT vs OAuth, Cursor / Claude Code / Claude Desktop, and Copy prompt. Hive AI settings still apply — MCP calls use the same provider, key, and token cap.

Documents · Agents · AI settings · Plans