Data Dive API & MCP: How to Create an API Key and Connect AI Tools

Data Dive supports two ways to work with your account outside the Data Dive interface:

• API access for scripts, applications, and custom integrations.
• MCP (Model Context Protocol) for connecting AI tools such as Claude, Claude Code, Cursor, ChatGPT, and other MCP-compatible clients.

Which should I use?

Before You Begin

API and MCP access are available on Standard and Enterprise plans. Starter plans do not include either feature.

The dedicated MCP Access role lets a team member connect AI tools to Data Dive without giving them permission to manage the organization API key. MCP Access is already included with the Admin and Billing roles.

Create a Data Dive API Key

Use an API key when you want to call Data Dive directly from your own application, script, or integration.

1. Open the Data Dive API page.
2. Create an API key from the controls shown on the page.
3. Copy the key and store it somewhere secure.
4. Use the key according to the authentication instructions in the Data Dive API documentation.

Keep your API key secure

Treat the API key like a password:

• Do not post it publicly or include it in screenshots.
• Avoid committing it to source control.
• Store it in a secure secret or environment-variable system when using it in an application.
• Only share it with systems or people that are authorized to access your Data Dive organization.

Return to the API page in your Data Dive account whenever you need to manage your organization's API access.

Connect Data Dive to AI Tools with MCP

MCP allows a compatible AI assistant to use supported Data Dive tools directly from a conversation.

You do not need to paste your Data Dive API key into the AI assistant. MCP uses a separate authorization flow tied to your Data Dive organization.

Connect Claude

Data Dive is available in the Claude connector directory.

1. Open Data Dive in the Claude connector directory
2. Click Connect in Claude.
3. Claude will send you to Data Dive to authorize access to your organization.
   
4. Review the requested permissions and click Allow.
5. Return to Claude. The Data Dive connector should now show as Connected.

Claude Team and Enterprise workspaces

If your Claude workspace manages connectors at the organization level, an Owner may need to approve or add Data Dive first.

Members may see Request instead of Connect. Once the connector is approved for the Claude organization, the member can complete their own Data Dive authorization.

The Data Dive user must also have MCP Access, Admin, or Billing permissions in Data Dive.

Connect Claude Code, Cursor, ChatGPT, or Other MCP Clients

For other clients that support remote MCP servers, use the Data Dive MCP server:

https://mcp.datadive.tools/mcp

General setup:

1. Add Data Dive as a remote MCP server in the AI tool.
2. Use the Data Dive MCP server URL above.
3. Complete the Data Dive authorization flow when prompted.
4. Approve the permissions you want the connection to have.

MCP setup and approval screens vary between AI products, plans, and workspaces.

For current tool-specific instructions, see the Data Dive MCP page.

Understand MCP Permissions

There are several separate permission layers involved when using MCP.

Data Dive organization permission

Your Data Dive user must have permission to use MCP.

The MCP Access role allows a user to connect AI tools without granting broader Admin access or access to manage the organization's API key.

MCP Read and Write scopes

When an AI tool connects to Data Dive, the authorization screen shows the scopes being granted.

Read Access is included with the connection. Write Access is optional.

Write actions can include operations such as running a Niche Dive, creating a Rank Radar, adding tracked search terms, or generating supported listing content.

Some of these actions consume Data Dive tokens or other plan resources.

AI-tool permissions

The AI client may have its own permission system in addition to Data Dive's authorization.

For example, Claude may ask you to approve tool use or a specific action inside the conversation.

A connection therefore may have permission in Data Dive while still requiring approval inside the AI tool before an action can run.

Token-spending actions: In the current Claude connection flow, token-spending actions are presented for confirmation inside Claude before they are performed. Permission behavior in other MCP clients may differ.

What Can You Do With Data Dive MCP?

The available MCP tools may expand over time. Current capabilities include areas such as:

Example prompts

Once connected, you can ask things like:

• “Show me the Master Keyword List for this niche.”
• “Which keywords have lost rank over the last two weeks?”
• “Compare the competitors in this niche.”
• “Show me my Blind Spend alerts.”
• “What listing changes were detected for my products?”
• “How is my inventory distributed?”
• “Create a Rank Radar for this product.”

If the request requires a capability the connection does not have, the AI tool should surface that limitation rather than receiving broader access automatically.

Manage MCP Connections and Team Access

View connected AI tools

Open the Data Dive MCP page to review connections authorized for your organization.

The page shows information such as:

• Connected tool
• Who authorized it
• Authorization date
• Read and Write scopes
• When it was last used

Multiple connections from the same AI product may appear when different users or sessions have authorized Data Dive separately.

Revoke a connection

Individual MCP connections can be revoked without changing or regenerating your Data Dive API key.

Revoking one connection does not revoke other authorized MCP connections.

Give a team member MCP access

Organization owners or admins can manage MCP access from the your User Management settings.

1. Open the team member.
2. Enable MCP Access.
3. Save the member.

Users with Admin or Billing roles already include MCP Access.

The MCP Access role allows the user to connect AI tools to Data Dive, but it does not give them permission to manage the organization API key.

Security and Privacy

API keys and MCP connections use separate authentication methods.

When you authorize MCP, the authorization screen identifies the Data Dive organization being accessed and the scopes being requested.

The connected AI tool can use the Data Dive information exposed through the MCP tools and scopes you authorize. It does not receive unrestricted access to every setting in your Data Dive organization simply because MCP is connected.

You can review and revoke MCP connections at any time from the Data Dive MCP page.

For more information about how Data Dive handles data, see the Data Dive Privacy Policy.

Troubleshooting

I can't access the API or MCP features

Confirm that your organization is on Standard or Enterprise.

For MCP, your Data Dive user also needs MCP Access, Admin, or Billing permissions.

If you are trying to manage the API key, make sure your user has the required organization permission for API-key management.

Claude shows Request instead of Connect

Your Claude Team or Enterprise workspace may require an Owner to approve the Data Dive connector before members can connect it.

Submit the request in Claude and complete your Data Dive authorization after the connector is approved.

My AI tool asks for an MCP server URL

Use:

https://mcp.datadive.tools/mcp

Then complete the Data Dive authorization flow.

I connected the tool but it cannot perform write actions

Check both permission layers:

1. Data Dive: Open the MCP page and confirm that the connection has Write Access.
2. The AI tool: Tools such as Claude may also require you to approve tool use or individual actions inside the conversation.

If the Data Dive connection only has Read Access, reconnect with Write Access enabled if you want that AI tool to perform supported write actions.

The connection used to work but has stopped

Open the Data Dive MCP page and confirm that the connection still exists.

If necessary, reconnect the AI tool and complete the Data Dive authorization flow again.

The assistant says a Data Dive action is unavailable

Possible reasons include:

• The connection only has Read Access.
• Your Data Dive user does not have MCP Access.
• The AI client does not support the required MCP capability.
• The requested action is not currently exposed through Data Dive MCP.
• The underlying Data Dive data or resource is unavailable.

If the same functionality is unavailable directly in Data Dive, contact Support.

Need Help?

If you have questions about API access, MCP setup, permissions, or plan availability, contact the Data Dive support team.