---
title: Orchestor Plugin
description: Add Orchestor skills, specialist agents, and an MCP connection to
  your AI tools.
canonical_url: https://orchestor.io/docs/en/agent-resources/orchestor-plugin
markdown_url: https://orchestor.io/docs/en/agent-resources/orchestor-plugin.md
contentType: how-to
---

# Orchestor Plugin

Orchestor Plugin adds Orchestor context, skills, specialist agents, and slash commands to compatible AI tools. Use your agent to investigate brands and AI answers, compare visibility, and inspect citation sources.

## Getting started

You need Node.js 24 or later and an AI tool. CLI workflows also require the [Orchestor CLI](https://orchestor.io/docs/en/cli.md) and workspace authentication.

### Installation

```bash
npx plugins add orchestor-inc/orchestor-plugin
```

Follow the installer to select your target. Claude Code also supports native installation:

```bash
claude plugin marketplace add orchestor-inc/orchestor-plugin
claude plugin install orchestor@orchestor
```

Start a new session after installation. In Claude Code, open `/mcp` and authorize Orchestor workspace access in your browser. CLI and MCP authentication are separate.

### Usage

In Claude Code, start with these commands:

```text
/orchestor:status
/orchestor:visibility Compare our brand with competitors over the last 30 days
/orchestor:monitor Add this question as a draft
```

## What the plugin provides

| Component | Purpose |
| --- | --- |
| Product context | Explains workspaces, brands, prompts, answers, and reports. |
| 17 Skills | Resource operations and AEO workflows that combine them. |
| 3 agents | Specialists for visibility analysis, monitoring, and connections. |
| 4 commands | `status`, `visibility`, `monitor`, `improve` |
| MCP | `https://mcp.orchestor.io/mcp` |

## AI tools

Claude Code installation and updates are verified. Codex installer registration is verified. The package also includes manifests for Cursor, GitHub Copilot CLI, Grok Build, and Kimi Code; authenticated runtime behavior is not verified across every tool. See the [repository compatibility table](https://github.com/orchestor-inc/orchestor-plugin#supported-tools).

## How it works

The SessionStart hook loads packaged product context and the skill entrypoint. It does not scan your project, access the network, or read credentials. Hook and command support varies by client.

## Skills and workflows

Resource skills cover brands, prompts, runs, reports, answers, and sources. Parent workflows combine the skills needed for an investigation or improvement proposal.

[Skill catalog and composition](https://orchestor.io/docs/en/agent-resources/skills.md)

## Updates

```bash
claude plugin marketplace update orchestor
claude plugin update orchestor@orchestor
```

Start a new session after updating. Choose one distribution route for the same skills to avoid duplicates between the Plugin and skills CLI.

## Telemetry

The Plugin itself sends no telemetry. Orchestor operations through the CLI or MCP are normal product requests.

## Reporting issues

Report problems in [GitHub Issues](https://github.com/orchestor-inc/orchestor-plugin/issues). Include your AI tool, the request, expected behavior, and actual behavior. Omit credentials and customer data.

---

[Documentation index](https://orchestor.io/docs/llms.txt)