Connect DAAAM to your AI.
DAAAM runs a local server that any MCP-compatible AI tool can query. Ask Claude, ChatGPT, Cursor, or any other connected AI about your footage. It searches your real archive and returns ranked results, timecodes, GPS locations, and file paths.
Your footage never leaves your machine. The AI connects to a local process. No cloud, no API key, no upload.
The easy way: from inside DAAAM.
DAAAM knows the exact paths on your machine. The Settings panel generates the right config for you. No guessing, no editing paths by hand.
- Claude Desktop: toggle the switch. DAAAM writes the config file for you. Restart Claude Desktop and you're done.
- Any other client: click Copy config to get the JSON block for your machine, or Copy command for the one-liner.
Claude Desktop
The one-click path. DAAAM handles the config file automatically, so you don't need to touch any JSON.
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge in the block from DAAAM Settings. Create the file if it doesn't exist.
{
"mcpServers": {
"daaam": {
"command": "/Applications/DAAAM.app/Contents/MacOS/dam_api",
"args": ["mcp"],
"env": {
"DAM_DB_PATH": "/Users/you/Library/Application Support/ai.daaam.desktop/dam_index.db"
}
}
}
}The exact command and DAM_DB_PATH values are specific to your machine. Copy them from DAAAM Settings → Connect to AI → Copy config. Do not use the placeholder paths above.
Claude Code
Claude Code (the CLI) uses the claude mcp add command. Copy the exact command from DAAAM Settings. It has your real paths already filled in.
claude mcp add daaam --env DAM_DB_PATH="/path/to/dam_index.db" -- "/Applications/DAAAM.app/Contents/MacOS/dam_api" mcpThis registers DAAAM with Claude Code globally. The real command from Settings has your actual paths, so don't use this placeholder.
claude mcp list and you should see daaam in the list.ChatGPT Desktop
ChatGPT Desktop (Mac and Windows) supports MCP servers. The config format is the same JSON block, just in a different file.
On macOS, the file is at:
~/Library/Application Support/com.openai.chat/mcp_servers.jsonOn Windows:
%APPDATA%\OpenAI\ChatGPT\mcp_servers.jsonCreate the file if it doesn't exist. ChatGPT also exposes MCP settings through Settings → Integrations in newer versions, so check there first.
mcpServers format as Claude Desktop. If the file already has other entries, merge the daaam key in rather than replacing the whole file.{
"mcpServers": {
"daaam": {
"command": "/Applications/DAAAM.app/Contents/MacOS/dam_api",
"args": ["mcp"],
"env": {
"DAM_DB_PATH": "/Users/you/Library/Application Support/ai.daaam.desktop/dam_index.db"
}
}
}
}Cursor
Cursor supports MCP servers. Add DAAAM globally (for all projects) or per-project.
Global (works in all projects):
~/.cursor/mcp.jsonPer-project (only for the current workspace):
.cursor/mcp.jsonPaste the mcpServers block into whichever file you choose. Create it if it doesn't exist.
{
"mcpServers": {
"daaam": {
"command": "/Applications/DAAAM.app/Contents/MacOS/dam_api",
"args": ["mcp"],
"env": {
"DAM_DB_PATH": "/Users/you/Library/Application Support/ai.daaam.desktop/dam_index.db"
}
}
}
}Any other MCP-compatible client
Windsurf, Continue, Cherry Studio, and any other tool that supports the MCP standard all use the same config format. Get the JSON block from DAAAM Settings and follow that tool's documentation for where to place it.
The block to add is always the same:
{
"mcpServers": {
"daaam": {
"command": "/Applications/DAAAM.app/Contents/MacOS/dam_api",
"args": ["mcp"],
"env": {
"DAM_DB_PATH": "/Users/you/Library/Application Support/ai.daaam.desktop/dam_index.db"
}
}
}
}Copy your actual config from DAAAM Settings → Connect to AI. The paths above are placeholders.
Six tools. Everything your AI needs to navigate your archive.
Once connected, your AI has access to these tools, available in Claude, ChatGPT, Cursor, or any other connected client.
| Tool | What your AI can do |
|---|---|
| Search your catalogue | Natural-language search using the same engine as the app. Filters by country, city, device type. |
| Browse your library | Page through every asset, newest first. Useful for "show me everything from the Zimbabwe trip." |
| Inspect a clip | Full metadata: vision captions, transcript, capture time, GPS, chunk count. |
| View your boards | List all storyboards and collections. Get the ordered frames in any board. |
| Check what's indexed | Asset count and database path, confirming there's a catalogue before running queries. |
| Drive awareness | Every result reports the physical drive the original lives on, and whether it's mounted. |
Your archive. Your AI's context.
Ask your AI about your footage the same way you'd ask a colleague who'd watched every clip.