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.

What this is

Every agent in this marketplace talks to your files through the official Kiteworks MCP connector — a small, Kiteworks-provided connector that Claude signs in to. The agents are the plugins you install; the connector is the secure pipe they use to reach Kiteworks. They are two different things.

This page covers how the connector gets connected, and how to add it yourself. Pick the path that matches you:

  • Most people: do nothing here — the agent connects it for you on first use. See *Easiest path*.
  • Prefer to connect it first, in the app: add it from Claude's Connectors directory. See *Add it yourself (Claude web / Desktop)*.
  • Admins / Claude Code / power users: run the connector yourself. See *Add it yourself (terminal and Claude Code)*.

Easiest path — the agent connects it for you

You usually do not set anything up by hand. When you install an agent and first ask it for 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. That's it.

Check whether it's already there: open Claude web or Desktop, go to Settings, Connectors, and look under "Your connectors" for Kiteworks. Present and enabled means you're set.

Add it yourself (Claude web / Desktop)

Best when you want the connector in place before installing an agent, using the built-in directory — no downloads, no terminal.

  1. Go to claude.ai/settings/connectors (or Settings, Connectors in Claude Desktop).
  2. Click Browse directory and search "Kiteworks."
  3. Click Add, then sign in with your Kiteworks tenant when prompted.
  4. Confirm Kiteworks now appears under "Your connectors."

That's all — the agents pick it up automatically. The manual setup below is only for Claude Code or self-run installs.

Add it yourself (terminal and Claude Code)

Best when you run Claude Code, are an admin scripting setup, or want to run the connector binary directly.

First, get the kiteworks-mcp connector from the official repository at github.com/kiteworks/mcp (releases). Version 0.9.2 or newer is required. Confirm it is on your PATH:

kiteworks-mcp --version

Sign in once. The connector manages its own login and stores the token in your operating system's keychain — you never paste a token into a config file or into chat:

kiteworks-mcp login https://content.kiteworks.com

Use your own tenant host if it is not content.kiteworks.com.

Wire it into Claude Desktop (manual config)

Open Settings, Developer, Edit Config, and add a kiteworks entry:

{
  "mcpServers": {
    "kiteworks": {
      "command": "kiteworks-mcp",
      "args": ["start", "https://content.kiteworks.com"]
    }
  }
}

Restart Claude Desktop. The Kiteworks tools now appear in the connector list.

Wire it into Claude Code

From a terminal:

claude mcp add kiteworks -- kiteworks-mcp start https://content.kiteworks.com

Verify with claude mcp list — you should see kiteworks connected.

Tool safety — what the connector can do

The connector exposes a read, browse, search and identity tool set by default. The agents in this marketplace only use the read-only ones (they report on your content; they never move, modify, or delete anything — see What to expect).

  • Destructive tools are off by default. Move and delete tools (move_file, move_folder, delete_file, delete_folder) only turn on if you add the -enable-destructive-tools flag when starting the connector. The agents here never use them. Do not enable them unless you have your own reason to — an AI client with those tools on can delete your files with no undo. If you do enable it, the flag must come before the URL or the connector silently ignores it.
  • Some tools move file content. read_file_contents pulls file text into the model's context and download_file_to_path writes file bytes to your disk. The agents in this marketplace are metadata-only by design and do not read file bodies; know that these content tools exist on the raw connector if you drive it yourself.

Security notes

  • No pasted secrets. Sign-in is handled by the connector's own login (token in the OS keychain) or by Claude's OAuth prompt. Never put a token or client secret in a config file or paste one into chat.
  • Read-only and best-effort. These agents report on Kiteworks content; they are productivity-grade, not the audited Kiteworks compliance runtime, and not a basis for a deletion or compliance decision on their own. See What to expect.