Does Brandfolder Have an MCP Server? What Exists in 2026 (and What Doesn't)

No. Brandfolder does not have a native MCP server as of July 7, 2026. Its parent company Smartsheet ships an official MCP server, but that server only reaches Smartsheet work data: sheets, reports, dashboards, workspaces. It exposes zero Brandfolder tools. If you want Claude or ChatGPT pulling assets out of Brandfolder today, you have three paths. An aggregator like Zapier, a community project built for one company, or a wrapper you build yourself on Brandfolder's REST API.

MCP (Model Context Protocol) is the open standard that lets AI tools like Claude, ChatGPT, and Copilot read and act on data in other systems. A DAM with an MCP server means your team's AI can search, fetch, and use approved brand assets directly. A DAM without one means downloading and pasting.

One honest disclosure before we go further: I run Masset, a content platform that competes with Brandfolder. So I'm biased. That's exactly why every claim below links to the page I checked, with the date I checked it. If Brandfolder ships an MCP server, this article gets updated.

Smartsheet bought Brandfolder in September 2020 for about $155 million. Since then, Brandfolder's developer docs have lived on Smartsheet's portal. That's where the confusion starts.

Search "brandfolder mcp server" and Google hands you Smartsheet MCP pages that look like the answer. They're official. They're well documented. And they're about a completely different product. The Smartsheet MCP server connects AI to your project grids, not your brand assets.

I get why people conflate them. Same parent company, same developer portal, same word ("assets") used in two different ways. But if you connect the Smartsheet MCP server hoping to ask Claude for your latest approved logo, you'll get sheets and dashboards back. Nothing else.

Credit where it's due: Smartsheet shipped a real MCP server. It went generally available on March 24, 2026. It requires a Business, Enterprise, or Advanced Work Management plan. Claude gets a direct connector inside Smartsheet's settings. ChatGPT, Microsoft 365 Copilot, Gemini Enterprise Plus, and Amazon Quick have connectors too. Any other MCP client can connect with OAuth or a personal access token.

The coverage is genuinely useful if your team lives in Smartsheet grids. Roughly 41 documented tools: searching sheets, adding and updating rows, creating reports and dashboards, browsing workspaces and folders, managing attachments, discussions, and shares.

None of it touches Brandfolder. I searched the full tools reference for the word "Brandfolder" and it appears zero times. And watch the word "assets" on that page. In Smartsheet's MCP docs, "assets" means work items like sheets, reports, and dashboards, not the files in your DAM. That one word does most of the damage in this search result.

Your AI client can reach the Smartsheet MCP server and its roughly 41 tools for sheets, reports, dashboards, and workspaces. Brandfolder, where your logos, photos, and videos live, has no connection to any of it.

A negative claim ("there is no MCP server") deserves more proof than a positive one. So instead of asking you to trust me, this is the full list of official surfaces I checked on July 7, 2026.

In plain words: the Brandfolder homepage and product pages never mention MCP. The Brand Intelligence page describes tagging AI, not agent access. The developer docs cover a REST API v4 with no MCP section. The Smartsheet MCP tools reference lists about 41 tools and never says the word Brandfolder. And Brandfolder's own roadmap post says they are "exploring generative AI and agentic AI opportunities," which is future tense. Smartsheet's earlier community MCP repo is deprecated in favor of the official server, which again covers Smartsheet only.

Also worth saying: I found no public statement, in either direction, about adding Brandfolder data to the Smartsheet MCP server. So the accurate phrasing is "no announced plans as of July 2026," not "never."

Brandfolder does have AI. It's called Brand Intelligence, and it's a machine-learning engine for organizing assets: automatic tagging, trainable models, and video scene and speech recognition. It powers the automated metadata tagging Brandfolder is known for.

The newest shipped piece is People Tagging, which uses facial recognition to tag who appears in your photos. Natural language search is announced as coming.

That's real, useful AI. It just lives on a different layer than what this search is asking about. Brand Intelligence helps a human search better inside Brandfolder. An MCP server lets your AI reach in from outside, pull the approved asset, and use it in the work it's already doing. Tagging AI and agent access solve different problems, and Brandfolder ships only the first one.

If you're on Brandfolder and want your AI tools talking to it anyway, four paths exist today. None of them are great, which is worth knowing before you spend a week on one.

Zapier MCP wraps Brandfolder's Zap actions, and those actions lean toward writing: create and update assets, collections, tags, and custom fields. Every MCP tool call burns two Zapier tasks against your plan, and Enterprise Zapier accounts aren't supported out of the box. viaSocket offers a similar generic endpoint with a free tier under a fair-usage policy, and even less Brandfolder-specific depth. DAM Butler is a community MCP server one enterprise customer built to bridge ChatGPT to Breville's internal Brandfolder instance. It inherits Brandfolder's permissions, which is the right design, but it was built for one company and isn't reusable without rebuilding it. The fourth path is doing that rebuild yourself. Brandfolder's v4 REST API is documented well enough to back a custom MCP wrapper, if you have an engineer who wants to own it.

The most telling fact in that list is DAM Butler. An enterprise Brandfolder customer wanted AI access to their DAM badly enough that they built their own MCP server. The demand is real. The product just isn't there.

Your team is already working inside Claude, ChatGPT, and Copilot. That's where drafts get written, campaigns get planned, and questions get asked. When the AI can hand your people the approved logo, the current deck, and the right case study mid-task, the DAM stays in the loop. When it can't, people grab whatever is on their desktop. A DAM your AI can't read becomes a filing cabinet your team stops opening.

We build for exactly this problem at Masset, so read the next paragraph knowing I'm biased.

Masset ships a native MCP server with 32 tools: 20 reads and 12 writes. It works with Claude, ChatGPT, Copilot, Cursor, and every MCP-compatible client, and every tool enforces the user's Masset permissions. If you're weighing the two platforms directly, the Masset vs. Brandfolder comparison covers pricing, features, and the AI gap in detail.

Brandfolder isn't alone here. Bynder sits in the same spot, and our breakdown of Bynder's MCP server walks through an almost identical gap. If you want the wider view of which DAMs can talk to AI and which can't, the MCP landscape section of our DAM buyer's guide lays out the whole field.

Take one question into your next vendor call: "Can my team's AI read our approved content through your platform, today, with our permissions enforced?" The answer will tell you more than any feature list.