Director CLI
Director bundles MCP servers, prompts and settings into playbooks and serves them to an agent through one endpoint, with central OAuth and tool filtering
- 482 ★ on the repository
- Last commit
- AGPL-3.0
Broad access
Why this level
- Holds OAuth access to connected MCP servers and proxies the agent's calls through its gateway
- The connect command rewrites configuration of Claude Code, Claude Desktop, Cursor and VS Code
- Starts MCP servers through npx and uvx, and the install script sets up Node, npm and uvx
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/fdmtl-directorDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Holds OAuth access to connected MCP servers and proxies the agent's calls through its gateway
- The connect command rewrites configuration of Claude Code, Claude Desktop, Cursor and VS Code
- Starts MCP servers through npx and uvx, and the install script sets up Node, npm and uvx
This is third-party code. Review the repository files before installing.
What it does
Director sits between an agent and MCP servers. A playbook is a set of MCP tools, prompts and settings for a particular task or environment, and you can keep many. The agent connects to a playbook with one command or by URL, so switching sets needs no hand-edited configs. The CLI is called director and installs as the @director.run/cli package. director create makes a playbook, director add puts a server from the registry into it, and director connect binds the playbook to a client: Claude Code, Claude Desktop, Cursor or VS Code. director studio opens a web interface for the same operations, and director mcp call-tool calls a playbook tool directly for testing. Among its features are tool filtering to keep context lean, shared OAuth sign-in for servers that need it, centralized JSON logs, and http2stdio, which turns an HTTP connection into a stdio stream. For embedding there is a TypeScript SDK, @director.run/sdk, and a Docker image.
Who it is for. For developers with many MCP servers wired into Claude Code, Cursor and other clients who want a short, separate set for each task.
Good fit when
- You have accumulated many MCP servers and need different tool sets for different tasks without rewriting client configs
- You want to leave an agent only some of a server's tools so the context is not spent on extra descriptions
- Several agents must reach the same OAuth servers with a shared sign-in
- You want a JSON log of the calls an agent makes
- MCP servers should run inside a Docker container rather than on the host
Not a fit when
- You run one or two MCP servers, and writing them straight into the client config is simpler
- You only need a server catalog for discovery, without a gateway between agent and servers
- The AGPL-3.0 license does not fit your project if you plan to embed Director's code
- The environment forbids the curl install script and you cannot install the package through npm
Example request
Create a Director playbook for documentation work, add the fetch server to it and connect it to Claude CodeLimitations
- AGPL-3.0 license.
- The service runs locally; for shared use you host it yourself: the README describes a Docker image and an SDK, not a hosted version to install.
- Clients with a ready connect command: Claude Code, Claude Desktop, Cursor, VS Code. For others you use the playbook URL by hand.
- The install script sets up Node, npm and uvx together with the CLI.
- Servers from the registry run on your machine through npx and uvx with your user's rights unless you run Director in Docker.
How to disable. director disconnect <playbookId> detaches a playbook from a client, and director destroy <playbookId> deletes it. Remove the CLI itself with npm uninstall -g @director.run/cli.
FAQ
What is a playbook in Director?
A set of MCP tools, prompts and settings for one task or environment. A playbook is built on the MCP tools and prompts primitives, connects to a client with a command and is also reachable at a single URL.
How do I connect a Director playbook to Claude Code?
Create a playbook with director create, add a server with director add and run director connect <name> --target claude. The connect command supports Claude Code, Claude Desktop, Cursor and VS Code.
How is Director different from connecting MCP servers directly?
The client sees one MCP endpoint instead of a list of servers, while Director filters tools, keeps a single OAuth sign-in and writes a shared JSON log. Playbooks can be swapped without touching the client config.
How do I install Director?
Run curl -LsSf https://director.run/install.sh | sh: it installs the CLI together with Node, npm and uvx. The alternative is npm install -g @director.run/cli. Then run director quickstart, which starts the gateway and opens the studio in a browser.
Does Director have a programmatic interface?
Yes, the TypeScript SDK @director.run/sdk: Gateway.start launches a gateway with a config, and playbookStore.create makes a playbook with a list of servers. The barnaby/director Docker image runs Director and the MCP servers inside a container.
Discussion
No questions or reviews yet.
Related
CLI toolsA universal MCP CLI client from Apify: persistent sessions, OAuth, JSON output for scripts and shell access to any MCP server for agents
A CLI that turns any MCP server, OpenAPI spec or GraphQL endpoint into commands at runtime, with no codegen
A zero-dependency Python CLI: one catalog of MCP servers and skills for every agent, with only a compact index in context
A CLI for any MCP server: list and call tools, resources and prompts, run mock and proxy modes, guard access and manage agent configs
An agent plugin that operates a deco Studio organization from the terminal under your own sign-in, through the decocms CLI
An MCP bridge: a single run_python tool runs code in a container and calls your MCP servers
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Director (this entry) | no | 482 | ||
| MCPM | no | 1,016 | a package manager and registry that installs MCP servers into clients, with no playbooks that bundle prompts | |
| capa | no | 718 | a package manager and MCP gateway where agent capabilities are declared in one capabilities.yaml file | |
| Docker MCP Gateway | yes | not required | 1,616 | Docker's gateway runs servers from the Docker catalog in isolated containers, with no studio or playbooks |
README in short
The project page calls Director a playbook layer for AI agents and opens with an install line. The overview lists playbooks, one-step connection, a shared endpoint, local-first operation, unified OAuth, tool filtering, logging and MCP spec compliance. Install steps, the web studio, a CLI command reference, a TypeScript SDK example and a list of the monorepo's apps follow: gateway, CLI, SDK, Docker, docs, registry and studio.