FAQs
How does authentication work?
The Masset MCP Server uses OAuth 2.0 with JWT Bearer tokens. When you add Masset as a connector in your AI client, the client handles the OAuth flow automatically. Each user connects their individual Masset account through the AI client’s Connectors settings, which grants the client a token scoped to that user’s permissions.
This means the MCP server respects the same access controls you have in Masset — you will only see assets and data you have permission to access.
What are the available scopes?
The Masset MCP Server uses the following OAuth scopes to control access:
Some tools additionally require specific permissions within your Masset account:
asset_analytics_searchandget_asset_activityrequire analytics permissions.list_collectionsrequires collections permissions.list_groupsrequires groups permissions.list_usersrequires users permissions.list_boardsrequires boards permissions.content_request_createrequires asset access permissions.- All
content_room_*tools require content room management permissions. - All
training_*tools require training management permissions; write tools additionally require EDIT permission on the target training session.
What is the rate limit?
The MCP server allows 60 requests per minute per authenticated user. Normal conversational usage is well within this limit. If you encounter rate limit errors (HTTP 429), wait briefly before continuing your conversation.
Which AI clients are supported?
The Masset MCP Server is compatible with any MCP-compatible client that supports Streamable HTTP transport. Currently documented clients include:
- Claude Web & Desktop (including Claude Cowork)
- Claude Code
- ChatGPT
If your AI client supports remote MCP servers via Streamable HTTP, it should work with the Masset MCP Server using the same endpoint and OAuth configuration.
What Masset data is accessible?
Through the MCP server, AI clients can access:
- Search results (asset names, descriptions, and rankings)
- Asset metadata (file details, tags, colors, detected objects, collections)
- Extracted text content (raw text, summaries, OCR text, transcriptions)
- JPEG preview images
- Analytics data (download, view, and share counts)
- Per-asset activity data (views, downloads, shares scoped by user or time window)
- Taxonomy information (categories, tags, collections)
- Organizational data (user groups, user details, collection membership, boards)
- Content rooms (shareable bundles, including their asset/board contents and CRM associations)
- Training session metadata, facts, questions, sources, leaderboards, and per-user stats
In addition, AI clients can take the following actions on the user’s behalf:
- Create and update content rooms, including associating them with HubSpot contacts, companies, or deals
- Submit content requests (new asset or asset change) that become tracked tasks in the Masset app
- Create, edit, and run training sessions — including AI-generating facts and questions — and transition them through their lifecycle (start, pause, resume, complete, cancel)
All data access and mutations are governed by the connected user’s Masset permissions. The MCP server never exposes data or performs actions that the user would not be able to do directly in Masset.
Is my data used for AI training?
No. Masset does not use your data for AI training. The MCP server simply provides your AI client access to your Masset content — it does not store, process, or use that data for any training purposes.
Data handling by the AI client (Claude, ChatGPT, etc.) is governed by that client’s own data policies and terms of service. Refer to your AI provider’s documentation for details on how they handle data.
Does the MCP server use any sub-processors?
The MCP Server does not currently use or require any additional sub-processors beyond the default set used by the Masset platform. If Masset introduces functionality requiring additional sub-processors in the future, these features will be explicitly opt-in for all customers.
Where can I submit feedback?
The Masset MCP Server is currently generally available and we welcome your feedback and suggestions. Your feedback is invaluable to help us expand the MCP server’s capabilities.
To submit feedback, bug reports, or feature suggestions, email us at support@getmasset.com.
