The Shade MCP
The Shade MCP connects your workspace directly to the AI tools and agents you already use , Claude, ChatGPT, Cursor, or any other MCP compatible client. Once connected, your assistant can search assets, read and update custom objects, build automations, and manage sharing and metadata, all from a prompt, without opening Shade.
Note: The Shade MCP is different from the Academy Shade MCP, which only answers questions about Shade's documentation. The Shade MCP connects to your live workspace and can read and modify your actual data.
Getting Started
Connect the Shade MCP from Settings → Integrate → MCP connections. You'll see pre-built options for the platforms we see used most often. If your platform isn't listed, copy the general MCP URL from this page and paste it into your client's custom connector field.

Claude
In Shade, go to Settings → Integrate → MCP connections.
Select Claude.
Follow the prompt to open Claude's connector settings.
Paste the provided URL into the custom connector field.
Sign in through OAuth to authorize the connection.
Test it with a prompt like:
Find all assets tagged "hero shot" in my Fall Campaign driveCreate a share link for this folder with comment permissions
ChatGPT
In Shade, go to Settings → Integrate → MCP connections.
Select ChatGPT.
Open your Tools or Connectors settings in ChatGPT.
Paste the provided URL when adding a custom connector.
Authorize the connection.
Test it with a prompt like:
Search my workspace for last week's uploadsList the custom objects in my Clients drive
Cursor
In Shade, go to Settings → Integrate → MCP connections.
Select Cursor.
Open Cursor's MCP settings and add the server.
Paste the provided URL.
Authorize the connection.
Test it with a prompt like:
Pull the metadata schema for my Deliverables object
Other MCP Clients
In Shade, go to Settings → Integrate → MCP connections.
Copy the general MCP URL.
Paste it into your client's custom connector or MCP server field.
Authorize the connection through OAuth.

What the Shade MCP Can Do
Once connected, you can review exactly what the MCP is allowed to do and set which actions require your approval from within your AI client's tool settings.
Manage (create, edit, and delete):
Automations
Collections
Comments
Files
Metadata
Custom objects
Share Links
Views
Read,only:
Browse Shade
Find duplicates
Get assets and asset previews
Get download URLs
Search
Access and read transcripts
List workspaces and drives
Example Workflows
Auto sync project management tools with custom objects: Connect another platform's MCP (Notion, Asana, ClickUp, HubSpot) alongside Shade's, then ask your LLM to pull the data from that tool and build a matching custom object in Shade. For example, "pull all the data from my Notion Content Calendar and set it up as a custom object, and sync both platforms daily at 5pm." Metadata fields and options carry over, and edits made on either platform reconcile on the schedule you set.
Build an automation from a prompt: Instead of building an automation block by block, describe the workflow directly. For example, "any time a file is uploaded to my rough exports folder, generate a share link with comment permissions and email it to [email protected] with the subject 'New Export Delivery.'" The MCP builds the automation to match.
Move data between connected tools: With Shade connected alongside other MCPs, an agent can act across platforms in one step, pulling a brief from a project management tool and gathering matching assets into a Shade collection, or pushing a generated share link back into an external tracker.
Things to Keep in Mind
The Shade MCP is separate from the Academy Shade MCP. Use the Academy MCP for documentation questions, and the Shade MCP for anything that touches your actual workspace.
Related
Last updated
Was this helpful?

