The CData MCP Server for Cvent defines each connection to Cvent as a named configuration that Claude can use when sending natural language queries.

You create and manage these configurations using the MCP Configuration Tool. The tool automatically handles formatting, storage, and registration with Claude Desktop.

Understanding Connection Configurations

Each connection configuration is stored in a .mcp file. This file includes the details needed to initialize the connector when Claude starts a session.

• On Windows, configuration files are stored in "~/AppData/Roaming/CData/Cvent Data Provider/".
• On macOS, configuration files are stored in "~/Library/Application Support/CData/Cvent Data Provider/".

The .mcp file is a text file that contains a list of connection properties and a timestamp. For example:

#Tue May 20 15:48:40 EDT 2025
AuthScheme=Basic
User=myUser
Password=myPassword
Security Token=myToken

The configuration tool handles these settings automatically. Each saved configuration enables Claude to launch a dedicated MCP Server instance with the correct connector and options. Manual file editing is not required.

The Cvent REST API uses the client credentials flow of OAuth 2.0 to authorize requests to the Cvent.

Before You Connect

Before you can authenticate to Cvent, you must create a workspace and an OAuth application.

Creating a Workspace

To create a workspace:

1. Sign into Cvent and navigate to App Switcher (the blue button in the upper right corner of the page) > Admin.
2. In the Admin menu, navigate to Integrations > REST API.
3. A new tab launches for Developer Management. Click on Manage API Access in the new tab.
4. Create a Workspace and name it. Select the scopes you would like your developers to have access to. Scopes control what data domains the developer can access.
   • Choose All to allow developers to choose any scope, and any future scopes added to the REST API.
   • Choose Custom to limit the scopes developers can choose for their OAuth apps to selected scopes. To access all tables exposed by the server, you need to set the following scopes:
     • event/attendees:read
     • event/attendees:write
     • event/contacts:read
     • event/contacts:write
     • event/custom-fields:read
     • event/custom-fields:write
     • event/events:read
     • event/events:write
     • event/sessions:delete
     • event/sessions:read
     • event/sessions:write
     • event/speakers:delete
     • event/speakers:read
     • event/speakers:write
     • budget/budget-items:read
     • budget/budget-items:write
     • exhibitor/exhibitors:read
     • exhibitor/exhibitors:write
     • survey/surveys:read
     • survey/surveys:write

Creating an OAuth Application

After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See Creating a Custom OAuth Application for a procedure.

Connecting to Cvent

After creating an OAuth application, set the following connection properties to connect to Cvent:

• InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
• OAuthClientId: The Client ID associated with the OAuth application. You can find this on the Applications page in the Developer Portal.
• OAuthClientSecret: The Client secret associated with the OAuth application. You can find this on the Applications page in the Developer Portal.