Installation

Set up the Masset MCP Server in your preferred AI client

Setup overview

Before starting, determine which AI client components you would like to support. You may need to install the Masset MCP Server multiple times in order to support all components. Also determine if you are installing the MCP server for yourself or for your entire organization.

Masset recommends installing the MCP server once for your entire organization, if possible. This greatly simplifies management of the connector. Because Masset has unlimited user seats, it costs you nothing to install it for your entire organization.

Installation

The Masset MCP Server is installed as a Custom Connector in the Claude interface. The installation steps differ depending on your Claude subscription plan.

To install the Masset MCP Server for your organization:

2

Click 'Add custom connector'

Click the “Add custom connector” button at the bottom of the section.

3

Enter the connector details

Enter the following fields. You may need to expand Advanced Settings to see the OAuth fields.

FieldValue
NameMasset
Remote MCP server URLhttps://app.getmasset.com/api/v1/mcp
OAuth Client IDclaude-mcp
OAuth Client Secretleave blank
4

Click 'Add'

Finish configuring your connector by clicking “Add”.

Once a connector has been added to a Team or Enterprise organization, users still must individually connect to and enable that connector. This ensures that Claude can only access tools and data that the individual user has access to. See the Connecting your Masset account section below.

If you do not have a Claude Team or Claude Enterprise subscription, each user will need to install the MCP server for themselves.

2

Click 'Add custom connector'

Click the “Add custom connector” button at the bottom of the section.

3

Enter the connector details

Enter the following fields. You may need to expand Advanced Settings to see the OAuth fields.

FieldValue
NameMasset
Remote MCP server URLhttps://app.getmasset.com/api/v1/mcp
OAuth Client IDclaude-mcp
OAuth Client Secretleave blank
4

Click 'Add'

Finish configuring your connector by clicking “Add”.

Connecting your Masset account

Once installed, the Masset connector must be connected to your Masset account. Each user that wants to use the Masset connector will be required to connect their own account. This ensures that Masset permissions are honored and that your favorites and preferences are applied.

2

Locate the Masset connector

Find and select the “Masset” connector in the Connectors section.

3

Click 'Connect'

Click the “Connect” button next to the Masset connector.

4

Login to Masset

You will be redirected to login to the Masset application. If you are already logged in, you will automatically be taken back to the Claude interface.

Your Masset connection is now established. You can start using Masset in conversations.

Using Masset in conversations

Click the ”+” button on the lower left of the chat interface, then select “Connectors” and enable “Masset”. Claude will automatically discover and use the available Masset tools when relevant to your conversation.

Troubleshooting

Verify that the server URL is entered exactly as https://app.getmasset.com/api/v1/mcp. Ensure you have a stable internet connection and that your network does not block outbound HTTPS connections to app.getmasset.com.

Make sure the OAuth Client ID is set to claude-mcp and the OAuth Client Secret field is left blank. If you continue to see authentication errors, try disconnecting and reconnecting your Masset account in the Connectors settings.

Ensure you have completed both the installation step (adding the connector) and the connection step (authenticating with your Masset account). If tools still do not appear, try toggling the Masset connector off and on again in your conversation settings.

The Masset MCP Server allows 60 requests per minute per user. Normal conversational usage is well within this limit. If you encounter rate limit errors, wait a moment before continuing your conversation. If you are using an agentic workflow that makes many rapid requests, consider adding pauses between tool calls.