Performm MCP Server

Talk to all of
your storage.

The first MCP server for enterprise storage. Connect any AI agent to every Performm tool, on every storage system you use. Built on the open Model Context Protocol. Available on every plan.

One MCP · 90+ endpoints · Every Performm tool
claude · performm-mcp-session
Find my latest Apple Q4 promo footage
// thinking...
// using performm.search

Found Apple_Q4_Promo_v7.mov
source: aws-studio-master
size: 14.2 GB
modified: 3h ago by Sarah
duration: 2m 14s @ 4K

Transfer it to LucidLink so my editor can cut
// using performm.transfer
// initiated · ETA 2m 14s

Your AI agents can think. They can write.
They can't reach your files.

Storage was built before agents existed. The pipes weren't there. Until now.

MCP, for the storage your team already uses.

The Model Context Protocol is the emerging standard for connecting AI agents to tools and data. Claude uses it. Cursor uses it. Every major agent platform is converging on it. The Performm MCP gives any compatible agent access to every Performm tool, on every storage system you have connected.

01

An open protocol

MCP is an open standard from Anthropic. No vendor lock-in. Your agents and our server speak the same protocol, the same way Claude, Cursor, and any future MCP-compatible client will.

02

Every Performm tool, callable

Access, Search, Edit, Transfer, Sync, Collaborate, Migrate, Archive. Every tool in Performm is exposed as an MCP tool. Your agent gets the full storage toolkit, not a read-only slice.

03

Permissions and audit, baked in

Agents inherit your team's permissions. Every action is logged: which agent, on whose behalf, accessed which files, when. Governance is not an afterthought.

Performm has four ways in.
This is the one for your agents.

Every Performm operation is reachable through the desktop mount, the web app, the REST API, or an MCP-compatible agent. Same connection. Same 90+ endpoints. Same eight tools. Pick the door that fits how each part of your team works.

01 / Desktop

Native drives

Mount any storage system as a native drive. Open files in Premiere or Resolve like they're local.

02 / Browser

Web access

Access, share, and move files from the Performm web app. Nothing to install.

03 / API

REST API

Connect Performm to your product, pipelines, or third-party tools. Every tool, callable.

04 / Agents

MCP Server

Any MCP-compatible agent can search, move, and manage storage with permissioned access.

Three things that weren't possible before.

The Performm MCP unlocks workflows that previously required custom integration projects, manual scripts, or just weren't feasible at all. Three featured. Four more below.

More agent-enabled workflows.

The MCP makes new workflows tractable. These four are running in production at customers today.

04

Automated content lifecycle

An agent watches your active project drives and tiers cold files automatically after 60 days of inactivity. No custom scripts. No cron jobs. The agent calls Performm's Archive tool with policy-driven scoping.

"Archive any file in /projects untouched for 60+ days."
05

Self-service for non-technical teams

Marketing teams manage their own campaign assets through an internal AI chat. They share, expire, archive, and move files without filing tickets to IT. Performm enforces the permission boundaries.

"Share the brand guidelines with the agency. 7-day expiring link, latest version only."
06

Compliance-aware data movement

An agent moves EU customer data from US-region storage to Frankfurt, audits the entire migration, and flags files that didn't move. Performm exposes the Migrate tool with full audit logging that satisfies GDPR data residency.

"Move all EU customer data to Frankfurt. Audit and flag any failures."
07

AI training data preparation

A platform team building an internal model uses an agent to gather, transfer, and stage training datasets from multiple storage locations. The MCP lets the agent operate the full storage toolkit programmatically.

"Stage all 2024 customer transcripts to our training bucket. Deduplicate."

Every Performm tool, callable by your agent.

The MCP exposes the full Performm toolkit. Agents do not get a read-only slice. They get every operation, scoped by your team's permissions.

01 / Access
Find anything
"Find Apple_Q4_Promo across all our drives."
02 / Search
Cross-endpoint search
"Find all .prproj files modified this week."
03 / Edit
Open in editor
"Open the master edit on Marcus's desktop."
04 / Transfer
Cross-cloud move
"Move 1 TB of footage from S3 to LucidLink."
05 / Sync
Keep in lockstep
"Sync the campaign folder to all editor desktops."
06 / Collaborate
Team sharing
"Share brand assets with the agency. 7-day link."
07 / Migrate
Move whole datasets
"Migrate Q1 footage to cold storage. Audit it."
08 / Archive
Long-term searchable
"Archive everything older than 90 days."

Connect in minutes. Build in hours.

The Performm MCP is one URL, one API key, and a standard MCP connection. Compatible with every major agent client today. Built for the agent ecosystem tomorrow.

For Claude or Cursor

Add Performm to your MCP config. Your agent immediately gains access to every Performm tool, scoped to your team's permissions.

No SDK to install. No glue code. No per-provider connectors. One URL.

For custom agents

Build your own MCP client in JavaScript, TypeScript, Python, or any language with an MCP library. Performm exposes the standard MCP tool-call interface.

// ~/Library/Application Support/Claude/claude_desktop_config.json { "mcpServers": { "performm": { "url": "https://mcp.performm.co/your-workspace", "apiKey": "${PERFORMM_API_KEY}" } } } // That's it. Claude now has access to every Performm tool, // scoped to your team's permissions.

Agents inherit your team's permissions.

An agent should never see a file the human it acts for cannot see. Every MCP request is permission-checked against your existing Performm roles. Every action is logged with the human-in-the-loop context.

Permissions in action

Scoped tool access.

performm.search
All drives the user can see
Allow
performm.transfer
Active project drives only
Scoped
performm.archive
Policy-defined drives
Scoped
performm.delete
Requires human approval
Deny
performm.share.external
Requires human approval
Deny
Audit log preview

Every action, logged.

claude-desktop on behalf of sarah@studio.com called search for "Q4 promo"
2 min ago
cursor on behalf of marcus@studio.com called transfer on Apple_Q4_Promo_v7.mov
8 min ago
cost-optimizer on behalf of cto@studio.com called migrate on 4,287 files
1h ago
claude-desktop attempted delete on /projects/Q3. Denied, escalated to admin
3h ago
marketing-assistant on behalf of jen@studio.com called collaborate.share with 7-day link
yesterday

Works with the agent ecosystem you already use.

The Performm MCP is built on the open protocol. Any MCP-compatible client today works out of the box. The ones launching tomorrow will too.

Claude
Anthropic · Desktop & API
Cursor
IDE · MCP-native
Custom agents
Any language · Any framework
+ more, coming
The ecosystem is just starting

The Performm MCP is included.

Every Performm Cloud subscription includes the MCP Server at no additional cost. No per-agent fees. No per-call metering. No usage caps during beta. The agent layer is part of the platform, not a paid add-on.

$0
Per agent · Per call · Forever

Build with Performm MCP.

Beta opens early June, 2026. Get API access today. Your agents are waiting.