Shubhamsaboo/director is one of the open-source repositories TopGit tracks, currently at 91 stars. MCP Playbooks for AI agents
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Director allows you to provide playbooks to AI Agents. A playbook is a set of MCP tools, prompts and configuration, that give agents new skills. You can connect Claude, Cursor and VSCode in 1-click, or integrate manually through a single MCP endpoint.
Playbooks are portable, declarative YAML files that can easily be shared (or committed to version control). Director is local-first - installation and client integration takes 30 seconds. In addition, Director provides all of the MCP management functionality that you'd expect: tool filtering, logging, strong isolation, and unified OAuth.
📚 Playbooks - Maintain sets of tools, prompts and config for different tasks or environments.
🚀 1-Click Integration - Switch playbooks with a single click. Currently supports Claude Code, Claude Desktop, Cursor, VSCode
🔗 Shareable - Playbooks are flat files which can be shared or committed to version control easily.
🏠 Local-First - Director is local-first, designed to easily run on your own machine or infrastructure.
🔑 Unified OAuth - Connect to OAuth MCPs centrally, and use them across all of your agents.
🎯 Tool Filtering - Select only the MCP tools that are required for the specific task, preserving context.
📋 Declarative - Like terraform for AI agents, Director will enforce playbook to client mapping on startup.
🔧 Flexibility - You can configure director through the UI, by editing the config file, through the CLI or even using the Typescript SDK.
📊 Observability - Centralized JSON logging, that allows you to understand exactly what your agent is doing.
🔌 MCP Compliant - Just works with any MCP server or client. Up to date with the latest MCP spec.
Quickstart
# Install Director
$ curl -LsSf https://director.run/install.sh | sh
# Start the onboarding flow
$ director quickstart
Core Concepts
Playbooks
A playbook is a set of tools, prompts and configuration, used to provide specific capabilities to your agent. Under the hood, playbooks are built on top of the MCP tools & prompts primitives.
The easiest way to author a playbook is via the UI (director studio). But you can also use the CLI or write the config manually (see below). You can have many playbooks, typically one per task or per environment. Connecting them is one click in the UI (or one CLI command / config entry), connections are enforced on startup.
# Client <> Playbook mappings (enforced on startup)
clients:
cursor: [ demo ]
playbooks:
- id: demo
name: demo
description: A demonstration playbook
#
# Prompts
#
prompts:
- name: changelog
title: changelog
description: ""
body: "write a short changelog based on recent changes on the
director-run/director repository and the post it to to the slack
#general channel. Make sure the message will format correctly inside
of slack"
#
# MCP Servers
#
servers:
# GitHub server
- name: github
type: http
url: https://api.githubcopilot.com/mcp/
headers:
Authorization: Bearer
<YOUR_GITHUB_TOKEN>
# This server is enabled
disabled: false
# Only include the tools you need
tools:
include:
- list_commits
- search_pull_requests
- get_latest_release
# Prompts from MCP server are disabled by default
prompts:
include: []
- name: slack
type: stdio
command: npx
args:
- -y
- "@modelcontextprotocol/server-slack"
env:
SLACK_TEAM_ID: <YOUR_SLACK_TEAM_ID>
SLACK_BOT_TOKEN: <YOUR_SLACK_BOT_TOKEN>
SLACK_CHANNEL_IDS: <YOUR_SLACK_CHANNEL_ID>
# This server is enabled
disabled: false
# Only include the tools you need
tools:
include:
- slack_list_channels
- slack_post_message
# Prompts from MCP server are disabled by default
prompts:
include: []
Architecture
At a high level, Director is a service that sits between your agents and MCP servers. It's transparent to clients, requiring no additional tokens. It models playbooks, which can be thought of as standalone, portable skills that enhance your AI agent with new capabilities.
Usage
Installation
# Install the director CLI + dependencies (node, npm & uvx) via the 1-liner:
$ curl -LsSf https://director.run/install.sh | sh
# Alternatively, install through npm:
$ npm install -g @director.run/cli
# Start director & open the UI
$ director quickstart
The Studio (Web UI)
The simplest way to interact with director is via the admin interface:
# Open studio in your browser
$ director studio
CLI Reference
Playbooks for your AI agent
USAGE
director <command> [subcommand] [flags]
CORE COMMANDS
quickstart Start the gateway and open the studio in your browser
serve Start the web service
studio Open the UI in your browser
ls List playbooks
get <playbookId> [serverName] Show playbook details
auth <playbookId> <server> Authenticate a server
create <name> Create a new playbook
destroy <playbookId> Delete a playbook
connect <playbookId> [options] Connect a playbook to a MCP client
disconnect <playbookId> [options] Disconnect a playbook from an MCP client
add <playbookId> [options] Add a server to a playbook.
remove <playbookId> <serverName> Remove a server from a playbook
update <playbookId> [serverName] [options] Update playbook attributes
http2stdio <url> Proxy an HTTP connection (sse or streamable) to a stdio stream
env [options] Print environment variables
status Get the status of the director
REGISTRY
registry ls List all available servers in the registry
registry get <entryName> Get detailed information about a registry item
registry readme <entryName> Print the readme for a registry item
MCP
mcp list-tools <playbookId> List tools on a playbook
mcp get-tool <playbookId> <toolName> Get the details of a tool
mcp call-tool <playbookId> <toolName> [options] Call a tool on a playbook
PROMPTS
prompts ls <playbookId> List all prompts for a playbook
prompts add <playbookId> Add a new prompt to a playbook
prompts edit <playbookId> <promptName> Edit an existing prompt
prompts remove <playbookId> <promptName> Remove a prompt from a playbook
prompts get <playbookId> <promptName> Show the details of a specific prompt
FLAGS
-V, --version output the version number
EXAMPLES
$ director create my-playbook # Create a new playbook
$ director add my-playbook --entry fetch # Add a server to a playbook
$ director connect my-playbook --target claude # Connect my-playbook to claude
Configuration File Reference
#
# Server config
#
server:
# Defaults to 3673
port: 1234
#
# Client <> Playbook mappings (enforced on startup)
#
clients:
cursor: [ demo ]
playbooks:
- id: demo
name: demo
description: A demonstration playbook
#
# Prompts
#
prompts:
- name: changelog
title: changelog
description: ""
body: "write a short changelog based on recent changes on the
director-run/director repository and the post it to to the slack
#general channel. Make sure the message will format correctly inside
of slack"
#
# MCP Servers
#
servers:
# GitHub server
- name: github
type: http
url: https://api.githubcopilot.com/mcp/
headers:
Authorization: Bearer
<YOUR_GITHUB_TOKEN>
# This server is enabled
disabled: false
# Only include the tools you need
tools:
include:
- list_commits
- search_pull_requests
- get_latest_release
# Prompts from MCP server are disabled by default
prompts:
include: []
- name: slack
type: stdio
command: npx
args:
- -y
- "@modelcontextprotocol/server-slack"
env:
SLACK_TEAM_ID: <YOUR_SLACK_TEAM_ID>
SLACK_BOT_TOKEN: <YOUR_SLACK_BOT_TOKEN>
SLACK_CHANNEL_IDS: <YOUR_SLACK_CHANNEL_ID>
# This server is enabled
disabled: false
# Only include the tools you need
tools:
include:
- slack_list_channels
- slack_post_message
# Prompts from MCP server are disabled by default
prompts:
include: []
TopGit's last sync did not record any GitHub topics for Shubhamsaboo/director. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on Shubhamsaboo/director?
The most recent commit recorded on Shubhamsaboo/director was 1.1 years ago, based on the GitHub push timestamp. The repository has 22 forks — one of the better signals of community interest.
How many stars does Shubhamsaboo/director have?
Shubhamsaboo/director has 91 GitHub stars — refresh the page for the live number, or check github.com/Shubhamsaboo/director. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is Shubhamsaboo/director written in?
TopGit's last sync did not record a primary language for Shubhamsaboo/director. Open the repository on GitHub to see the full breakdown by file extension.
Where do I read more about Shubhamsaboo/director?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/Shubhamsaboo/director is the definitive source.
Read full README in the tab above.
Is director worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of director.