# Playbook MCP Server | Connect Your Asset Library to Any AI Tool

> Playbook speaks the Model Context Protocol (MCP), so Claude, ChatGPT, Cursor
> and any other MCP client can reach your asset library directly. One URL to
> connect. Nothing to build.

## At a glance

- **Connector URL** — `https://mcp.playbook.com`
- **Works with** any MCP client, including Claude, ChatGPT and Cursor
- **Setup** — paste the URL into your tool's connector settings, authorize once
- **No code required** — the REST API is available separately for custom builds

## Connect

1. **Copy the connector URL** — `https://mcp.playbook.com`
2. **Add it in your tool** — Claude: Settings → Connectors → add a custom
   connector. ChatGPT: Settings → Apps. Cursor: add it to `.cursor/mcp.json`,
   or install it from Cursor's MCP directory.
3. **Sign in once** — authorize Playbook, then ask for what you need.

## Headline tools

- **`ai_search` — Find it by what it looks like.** Describe the shot and get
  matches, no tags required.
- **`search_assets` — Filter across everything at once.** Tags, status, custom
  fields, file type, uploader, combined in a single query.
- **`list_assets` — Read the whole library, not a page of it.** Walks the full
  board tree in one pass, nested boards included.
- **`update_asset` — Write the metadata back.** Titles, tags, custom fields,
  board placement.
- **`set_asset_approval` — Change state on a thousand assets at once.** One
  call, across boards, approved or not.
- **`upload_from_urls` — Bring a hundred files in per call.** Fetched, routed
  to the right board, titled and tagged on the way in.

## Full toolset

- **Search and read**: `ai_search`, `search_assets`, `list_assets`,
  `get_assets`, `get_asset_previews`
- **Boards**: `list_boards`, `list_board_children`, `get_board`,
  `create_board`, `update_board`, `copy_assets`, `move_assets`
- **Metadata**: `update_asset`, `update_asset_status`, `change_asset_tags`,
  `set_asset_approval`, `list_custom_fields`, `create_custom_field`
- **Versions**: `create_asset_version`, `list_asset_versions`, `revert_asset`
- **Sharing**: `share_board`, `publish_board`, asset permalinks
- **Comments and notes**: `get_comments`, `create_comment`, `create_note`
- **Uploads**: `upload_from_urls`
- **Workspace**: `list_organizations`, `list_members`
- **Destructive**: `delete_asset`, `delete_board`, `delete_custom_field`

## FAQ

**What is MCP?**

MCP (the Model Context Protocol) is an open standard for connecting AI
assistants to outside tools and data. An app publishes an MCP server, and any
MCP client can use it. Playbook publishes one, so an assistant can work with
your workspace directly instead of you copying files into a chat.

**Which AI tools can I connect?**

Any client that speaks MCP. Claude, ChatGPT and Cursor are the ones teams ask
for most, but the same connector URL works anywhere else.

**What can the assistant see and do?**

It connects as you and works inside your account's permissions: it reaches the
boards and assets you can already reach, and nothing that hasn't been shared
with you. It can also make changes, the same ones you can make yourself.
Tagging, filing, versioning, approving, creating boards, sharing, and bringing
in files from a URL.

**Can it break anything?**

Deleting is a soft delete: anything removed goes to your Playbook trash and can
be restored. The assistant is also instructed to confirm with you before
deleting anything. On plans with version history, replacing a file keeps the
original as a version you can roll back to.

**Does it work across all my workspaces?**

Yes. One connection reaches every workspace your account belongs to, and the
assistant works in whichever one you name. If you don't say, it will ask.

**Do you train on my assets?**

No. Playbook does not use your assets to train models. Once an assistant is
connected, what it does with the files it retrieves is governed by that tool's
own data policy.

**Which plans include MCP?**

All of them, starting with Free. MCP requests count toward your plan's monthly
API calls: 1K on Free, 20K on Pro, 200K on Team, 5M on Business. See
[pricing](https://www.playbook.com/pricing/) for the full breakdown.

**How is this different from the API?**

MCP is for the assistant: it discovers what Playbook can do and calls it on your
behalf, in conversation. The REST API is for software you write. Both reach the
same workspace, and the [developer docs](https://dev.playbook.com) cover the
API.

## Links

- [MCP page](https://www.playbook.com/mcp/)
- [Developer docs](https://dev.playbook.com)
- [Pricing](https://www.playbook.com/pricing/)