Scenario A · Find and share
ZDAM tools called
- search_assets
- get_asset
- get_download_url
Your assistant searches the library, shows the matching shots as thumbnails in the chat, and returns a download link for each one. The links expire after an hour.
Your team already asks AI assistants for help. With ZDAM connected, the assistant can reach the real files, not just talk about them.
Search your library the way you'd ask a colleague. Your assistant finds the assets, shows thumbnails right in the chat, and hands back download links.
Every request runs with your own ZDAM permissions, inside your organization. Your assistant can't see or do anything you couldn't do yourself.
ZDAM ships a native server for the Model Context Protocol (MCP). Connect Claude Desktop, Claude.ai, or any assistant that supports MCP, with no plugins and no glue code.
One sentence in the chat. Behind it, your assistant calls ZDAM's tools, the same way you would click through the app.
Scenario A · Find and share
ZDAM tools called
Your assistant searches the library, shows the matching shots as thumbnails in the chat, and returns a download link for each one. The links expire after an hour.
Scenario B · Organize in one sentence
ZDAM tools called
The collection is created, the photos are added, and every one is tagged. Open ZDAM and it is all there, ready for the team.
Scenario C · Guardrails in action
ZDAM tools called
A contractor's assistant gets back only what that contractor can already see in ZDAM. Anything it changes or downloads is logged under the contractor's own account.
An assistant connected to ZDAM is held to the same rules as the person who connected it, with a few more on top.
How ZDAM handles securityStep 1
MCP access is included in the ZDAM Enterprise plan and switched on by default. Your ZDAM admin can turn it off for everyone at any time.
Step 2
In ZDAM, open Settings, then Personal Access Tokens, and create one. It is shown once, and you can give it an expiry date.
Step 3
Add ZDAM as a connector in Claude, or in any assistant that supports MCP, using your organization's ZDAM address and your token. Then just ask.
The Model Context Protocol is an open standard that lets AI assistants connect to outside tools and data. ZDAM ships a native MCP server, so an assistant can work with your asset library directly.
ZDAM works with Claude, including Claude Desktop and Claude.ai, and with any other assistant or agent that supports MCP.
Yes. It can upload files, tag assets, create collections, and add assets to them, all within your permissions. By default it can only make changes ZDAM can undo, and actions that can't be undone, such as permanently deleting files, are never available over MCP.
No. Every request runs as you, with your current ZDAM permissions. If you lose access to a folder, your assistant loses it at the same moment.
Yes. Everything an assistant changes, and every file it downloads, is logged in ZDAM under the person whose token was used, in the audit log and the activity history.
MCP access is included in the ZDAM Enterprise plan, and it is on by default. A ZDAM admin can turn it off for the whole organization at any time, which stops every token immediately.
Book a demo to watch an AI assistant search, share, and organize a live ZDAM library.