Configure P4 DAM access to P4 MCP Server

Configure P4 DAM access so that MCP-compatible AI assistants can access and manage content in P4 DAM. When access is enabled, AI-powered tools can search for assets, retrieve metadata, manage reviews, create asset bundles, and update asset tags.

P4 MCP Server is a Model Context Protocol (MCP) server that integrates with the P4 version control system. To learn more, see Perforce P4 MCP Server in the P4 Server Administration Documentation.

What you can do with P4 DAM through P4 MCP Server

When P4 DAM access is enabled in the P4 MCP Server, you can use MCP-compatible AI assistants to:

  • Search for assets by keyword, tag, project, repository, file type, date range, size, or user.

  • View full metadata for a single asset by depot path.

  • Render a thumbnail, preview, or raw file image.

  • Trigger asynchronous thumbnail, preview regeneration using P4 Search.

  • List P4 DAM projects.

  • List repositories in a P4 DAM project.

  • List P4 Server classic branches in a repository.

  • Create and manage asset bundles.

  • Sync an asset bundle's depot files to a local P4Client workspace.

  • List, create and manage file reviews.

  • Move reviews through workflow states.

  • Comment on a file review, a file within a review, a committed file, or reply to a comment.

  • View available workflows and workflow states.

  • Add and remove asset tags.

  • List custom attribute templates for a project.

  • Set or remove custom attribute values on assets.

  • Automate repetitive asset-management tasks in production pipelines.

Here are some sample queries you might send to an AI model when P4 DAM access is enabled in the P4 MCP Server.

  • "Find all released assets within the demo project."

  • "Show metadata for this asset."

  • "List all open asset reviews within the demo project created by admin."

  • "Create a review for this asset bundle."

  • "Show the available workflow states for the demo project."

  • "Add the approved tag to these assets."

  • "List repositories in this project."

Prerequisites

Before you use P4 DAM with P4 MCP Server, you need:

  • Access to a P4 DAM deployment.

  • A valid P4 Server ticket.

  • A valid P4 DAM API key.

  • A valid P4 DAM session for the account associated with the P4 DAM API key.

  • Access to a configured P4 MCP Server.

  • An MCP-compatible client, such as Claude Code, VS Code, Cursor, JetBrains IDEs, Eclipse, Kiro, or Windsurf.

For the most up-to-date prerequisites, see the Perforce P4 MCP Server README on GitHub.

Installation

To enable P4 DAM tools, configure a valid P4 DAM API key in the P4 MCP Server configuration. When the API key is present, the server registers P4 DAM tools and makes them available to MCP-compatible clients. To learn more about obtaining a P4 DAM API key, see Requests for managing API keys.

P4 MCP Server discovers the P4 DAM URL from the P4.HTH.URL property on the P4 Server. If this property is not configured, P4 DAM tool calls fail.

For complete and current installation steps, see the Perforce P4 MCP Server README on GitHub.

Limitations

Some MCP tools might require non-read-only mode or appropriate P4 permissions. General tool usage is restricted by configurations set by an administrator.

Support and licensing

P4 MCP Server is a community-supported project and is not officially supported by Perforce. Report P4 MCP Server issues to the GitHub community. For P4 issues, see the P4 Support portal.

P4 MCP Server is licensed under the MIT License. To learn more, see the license on GitHub.