The CData Code Assist MCP for Jira Assets defines each connection to Jira Assets as a named configuration that an MCP Client (such as Claude Desktop) can use when sending natural language queries.

You create and manage these configurations using the CData Code Assist MCP Configuration Tool. The tool automatically handles formatting, storage, and registration with MCP clients.

Understanding Connection Configurations

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

• On Windows, configuration files are stored in "~/AppData/Roaming/CData/Jira Assets Data Provider/".
• On macOS, configuration files are stored in "~/Library/Application Support/CData/Jira Assets 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 an MCP client to launch a dedicated MCP server instance with the correct connector and options. Manual file editing is not required.

Connecting and Authenticating to Jira Assets

Jira Assets supports connecting and authenticating via the APIToken.

To establish a connection, the URL connection property is required. This property must be set to the base URL of your Jira Assets (Atlassian Cloud) site, for example: https://your-domain.atlassian.net.

To generate an API token:

1. Log in to your Atlassian account.
2. Navigate to Security > Create and manage API Token > Create API Token.

Atlassian generates and then displays the API token.

After you have generated the API token, set these parameters:

• User: The login of the authenticating user.
• APIToken: The API token you just generated.

You are now ready to connect and authenticate to Jira Assets.