Kiteworks Agent Marketplace
Which AI assistant do you use?

Roll out Kiteworks agents to your organization

Three steps take a Claude organization from nothing to every member using Kiteworks agents: switch on Kiteworks MCP, connect each member, then hand out the agents.

  1. Turn on Kiteworks MCP for your tenant

    A Kiteworks administrator switches this on once for the whole tenant. Every agent depends on it.

    The Kiteworks MCP connector only works once an administrator has switched it on for your Kiteworks tenant — this is a one-time step done in the Admin Portal.

    1. In the Kiteworks Admin Portal, go to Application Setup → Apps and Plugins.
    2. Open the Kiteworks MCP tab, toggle Kiteworks MCP on, and click Save.
    3. Not an admin? Ask whoever manages your Kiteworks tenant to do this once.

    Full admin setup guide

  2. Connect each member to Kiteworks MCP

    Every member signs in to the Kiteworks MCP connector with their own Kiteworks account, so an agent only ever sees what that person can see in Kiteworks.

    Claude Desktop

    In Claude Desktop:

    1. Go to Customize → Connectors.
    2. Search for Kiteworks MCP Server and select it.
    3. Click Install, enter your Kiteworks instance URL (https://your.kiteworks.domain), and accept the Data Access Terms.
    4. Click Save, then use the toggle to turn the connector on.
    5. When a browser window opens, sign in to Kiteworks to authenticate.

    Claude Desktop setup guide

    Claude on the web

    In Claude on the web (claude.ai — custom connectors need a Max, Team, or Enterprise plan):

    1. Open claude.ai/settings/connectors.
    2. Click Browse connectors and search "Kiteworks."
    3. Click Add, enter your Kiteworks instance URL when prompted, and accept the data-access terms.
    4. Sign in with your Kiteworks tenant to authenticate.

    Kiteworks MCP connector guide

  3. Give every member the agents

    Register the Kiteworks marketplace once in your Claude organization, and members get the agents without installing anything themselves.

    Claude's org sync reads a marketplace repository through the Claude GitHub App, so it only works on a repository your own organization owns and can install that app on. Two routes:

    Mirror it for full admin control — one screen then decides what every member gets:

    1. Copy the Kiteworks marketplace into a private or internal repository your own organization owns — Anthropic does not accept a public repo here. Use GitHub's Import repository or a mirror push; a fork of a public repository stays public and cannot be made private.
    2. Install the Claude GitHub App on your copy.
    3. Go to Organization settings → Plugins, click Add plugins → GitHub, and enter your repository as owner/repo.
    4. Set "Kiteworks Agents" to Installed by default, or Required if members shouldn't be able to remove it. Enterprise plans can set this per group.
    5. Members see it next time they open Plugins — nothing for them to run. Re-sync your mirror when you want newer agents.

    Or upload the agents directly: from the same screen, upload each agent's .plugin file — no GitHub, no fork. Uploaded plugins don't update themselves, so you re-upload to move to a newer version.

    Full Claude install guide

  4. Rolling out Claude Code?

    Claude Code reads a managed settings file instead. The enterprise guide has the block that registers the marketplace on every machine.