Kiteworks Agent Marketplace
Which AI assistant do you use?

Install Kiteworks agents in Claude

Pick where you run Claude. Each path adds the same read-only marketplace — only the host differs.

Before you start

You need Claude — on the web, on Desktop, or in Claude Code — and a Kiteworks account for the tenant you want the agent to run against. Every agent is skill instructions plus the official Kiteworks MCP connector, with no separate backend to deploy. Each one declares the exact Kiteworks tools it can use up front, and runs as you, inside your own Kiteworks permissions and audit trail.

There are three ways in. Pick the one that matches you:

  • Just trying one agent? Add the marketplace once, install with one click — see "Try an agent (fastest)".
  • Rolling this out to a team? Mirror the marketplace into a repository your own organization owns, or hand out the agents directly — see "Roll it out to your team (admins)".
  • Live in the terminal or use Claude Code? Two commands — see "Terminal setup (Claude Code and power users)".

All of them deliver the same read-only agents. What differs is who hosts the copy, how many people get it, and whether updates arrive on their own.

Try an agent (fastest)

Best when you want to install a single agent for yourself in Claude on the web or Desktop. No terminal, no admin rights.

  1. Open Claude and click Customize in the left sidebar.
  2. Open the Plugins tab.
  3. Under "Personal plugins," click +, then Add marketplace.
  4. Enter https://github.com/kiteworks/claude-agent-marketplace.git and click Sync.
  5. Find "Kiteworks Agents" under Discover and click Install.

Already added the marketplace before? Skip straight to step 5 — open Customize, Plugins, find "Kiteworks Agents" under Discover, and install it with one click.

Then start a chat and ask for the agent by name. Browse what is available in the catalog.

Install a single agent (no marketplace)

Best when someone sent you one agent's .plugin file, or you want exactly one agent and nothing else.

  1. Download the .plugin file from that agent's catalog page.
  2. In Claude, open Customize, then Plugins.
  3. Click +, then Upload plugin, and choose the file you downloaded.
  4. The agent appears immediately under Installed.

This installs just that one agent and will not update automatically — the marketplace route (above) handles updates for you, so prefer it if you can.

Roll it out to your team (admins)

Best when you manage a Claude organization and want the Kiteworks agents in front of everyone, rather than asking each person to add the marketplace.

First, one thing to know about how Claude's org sync works. Under Organization settings, Plugins, Claude reads a marketplace repository through the Claude GitHub App — so the app has to be installed on that repository, and whoever switches on automatic sync needs admin rights on it. Both are things only the repository's owner can do. That makes org sync a way to publish your own repository to your own members; you cannot point it at the Kiteworks marketplace, because Kiteworks owns that repository. Three routes work instead.

1. Mirror it into your own repository

The full admin experience — one screen controls what every member gets.

  1. Copy https://github.com/kiteworks/claude-agent-marketplace.git into a private or internal repository your own organization owns — Anthropic does not accept a public repository for an organization marketplace. Use GitHub's Import repository, or push a mirror clone into a new private repo. Fork will not do: a fork of a public repository is public, and its visibility cannot be changed.
  2. Install the Claude GitHub App on your copy.
  3. In Organization settings, Plugins, click Add plugins, choose GitHub, and enter your own repository in owner/repo form.
  4. Set "Kiteworks Agents" to Installed by default, or to Required if members should not be able to remove it. On Enterprise plans you can set this per group.
  5. Members see it the next time they open Plugins — nothing for them to run.

Your copy does not track the Kiteworks repository on its own: re-sync the mirror when you want newer agents.

If your Organization settings has a Capabilities section, check that Cowork and Skills are enabled there before you start.

2. Upload the agents directly

No GitHub, no fork. From the same Organization settings, Plugins screen, upload each agent's .plugin file. Quickest way to get a handful of agents to a team — but uploaded plugins do not update themselves, so you re-upload to move everyone to a newer version.

3. Let people add it themselves

Nothing for you to host or maintain. Point your team at "Try an agent (fastest)" above: they add https://github.com/kiteworks/claude-agent-marketplace.git once, and it keeps itself up to date from then on. Not automatic for everyone, but there is no copy to keep in sync.

Terminal setup (Claude Code and power users)

Best when you run Claude Code or prefer the command line. Everything the GUI does, in two commands.

Register the marketplace once:

claude plugin marketplace add https://github.com/kiteworks/claude-agent-marketplace.git

Then install any agent by the exact plugin name shown on its catalog page:

claude plugin install <agent-name>@kiteworks-lite

Claude downloads the plugin directly from GitHub — there is nothing else to deploy. Pull the latest published versions any time with:

claude plugin marketplace update kiteworks-lite

Want to add the Kiteworks MCP connector yourself, or wire it into Claude Code directly? See Kiteworks MCP connector setup.

Connect Kiteworks

The first time an agent needs Kiteworks data, Claude prompts you to sign in through the official Kiteworks MCP connector. After that first sign-in the connection is reused for later sessions — you do not set anything up by hand.

If you would rather add the connector ahead of time, or you use Claude Code, the full walkthrough (GUI and terminal) is on the Kiteworks MCP connector setup page.

What to expect

  • Scoped. Each agent lists the exact Kiteworks tools it can call on its catalog page. Many are read-only; ones that move, modify, or send content say so, and act only within your own Kiteworks permissions.
  • Best-effort, not audited. These are productivity-grade tools driven by host instructions, not the audited Kiteworks Compliance Runtime — do not use their output as the sole basis for a compliance or deletion decision.
  • Updates. Marketplace-installed agents update through Claude; run claude plugin marketplace update kiteworks-lite (or re-sync in the GUI) to pull the latest published versions. Single uploaded .plugin files do not auto-update.