Claude for data teams: what seventeen data tools publish, and how to keep access in check

Claude for data teams means letting Claude work with the databases, spreadsheets and analytics tools a team already uses. Anthropic's directory lists connectors for many of them, and some makers publish an MCP server in the MCP Registry instead.

This page covers seventeen tools in plain terms. Each section uses only what the directory page or registry entry and the maker's own page said on 10 November 2026. Data access is the sensitive part, so the sections note where a maker says access is read-only or follows the signed-in user's permissions. Anthropic's directory pages carry the line "Only use connectors from developers you trust" and say Anthropic does not control which tools a developer makes available or verify that they work as intended.

Source: Anthropic connector directory (https://claude.com/connectors), read 10 November 2026.

A Claude Alpha Vantage integration is listed in Anthropic's directory, made by Alpha Vantage Inc. The directory describes stock market data, including prices, fundamentals, earnings, news sentiment, options and economic indicators, and says the page suits portfolio analysis and quantitative research.

Who uses it: analysts and finance teams who work with market data.

Alpha Vantage's own documentation says every request needs an API key, that a free key is available and that some features are premium.

Next step: Kriv AI's agentic AI and automation service covers putting Claude on your own data with written rules and a person accountable. See the agentic AI and automation page.

Sources: Anthropic directory, Alpha Vantage (https://claude.com/marketplace/connectors/alpha-vantage); Alpha Vantage, documentation (https://www.alphavantage.co/documentation/), read 10 November 2026.

For Claude with AppsFlyer (claude appsflyer integration), the position on 10 November 2026 is this. We found no page for it in Anthropic's connector directory on 10 November 2026. The AppsFlyer MCP server is listed in the MCP Registry as com.appsflyer/mcp, which is a different thing from a Claude connector, and the registry describes it as: "Analyze your campaigns any way you want, with AI."

This is the registry entry as read on 10 November 2026. We have not run it and make no claim about it.

Next step: Kriv AI's agentic AI and automation service covers putting Claude on your own data with written rules and a person accountable. See the agentic AI and automation page.

Sources: MCP Registry, com.appsflyer/mcp (https://registry.modelcontextprotocol.io/v0/servers?search=appsflyer), read 10 November 2026.

A Claude beehiiv integration is listed in Anthropic's directory, made by beehiiv. The directory says Claude can connect to your beehiiv workspace to draft, design and analyze.

Who uses it: newsletter and content teams that publish on beehiiv.

beehiiv's developer documentation index says AI clients such as Claude Code can connect to a documentation server at developers.beehiiv.com/_mcp/server, and that server describes itself as a search over the documentation. That is not the connector in the directory, so we found no maker page that states what the directory connector needs.

Next step: Kriv AI's agentic AI and automation service covers putting Claude on your own data with written rules and a person accountable. See the agentic AI and automation page.

Sources: Anthropic directory, beehiiv (https://claude.com/marketplace/connectors/beehiiv); beehiiv, developer documentation index (https://developers.beehiiv.com/llms.txt), read 10 November 2026.

A Claude ClickHouse integration is listed in Anthropic's directory, made by ClickHouse. The directory says Claude can browse ClickHouse Cloud services, databases and table schemas, run read-only SQL queries and check backups and billing costs.

Who uses it: data engineers and analysts on ClickHouse Cloud.

ClickHouse's own page says the remote server must be enabled for each service before it accepts connections, and that all its tools are read-only. It shows no beta label.

Next step: Kriv AI's agentic AI and automation service covers putting Claude on your own data with written rules and a person accountable. See the agentic AI and automation page.

Sources: Anthropic directory, ClickHouse (https://claude.com/marketplace/connectors/clickhouse); ClickHouse, remote MCP server (https://clickhouse.com/docs/cloud/features/ai-ml/remote-mcp), read 10 November 2026.

A Claude DataGrail integration is listed in Anthropic's directory, made by DataGrail, Inc. The directory describes automating privacy operations tasks, such as data subject reporting, with agentic workflows in Claude, and says human-governed actions are part of its design.

Who uses it: privacy and compliance operations teams that already run DataGrail.

DataGrail's own page says an administrator must enable external MCP access first, that Claude can only see data the signed-in user may view, and that the connector can return sensitive information that should not go to AI clients you do not trust. It shows no beta label. This page makes no compliance claim about DataGrail or about Kriv.

Next step: Kriv AI's agentic AI and automation service covers putting Claude on your own data with written rules and a person accountable. See the agentic AI and automation page.

Sources: Anthropic directory, DataGrail (https://claude.com/marketplace/connectors/datagrail); DataGrail, MCP introduction (https://docs.datagrail.io/docs/vera/vera-mcp/introduction-and-use), read 10 November 2026.

For Claude with GameAnalytics (claude gameanalytics integration), the position on 10 November 2026 is this. We found no page for it in Anthropic's connector directory on 10 November 2026. The GameAnalytics MCP server is listed in the MCP Registry as com.gameanalytics/analytics-docs, which is a different thing from a Claude connector, and the registry describes it as: "Search GameAnalytics docs: Unity, Unreal, iOS, Android SDK and API guides for mobile game analytics."

This is the registry entry as read on 10 November 2026. We have not run it and make no claim about it.

The description mentions only searching GameAnalytics documentation and says nothing about reading your own analytics data.

Next step: Kriv AI's agentic AI and automation service covers putting Claude on your own data with written rules and a person accountable. See the agentic AI and automation page.

Sources: MCP Registry, com.gameanalytics/analytics-docs (https://registry.modelcontextprotocol.io/v0/servers?search=gameanalytics), read 10 November 2026.

For Claude with MariaDB (claude mariadb integration), the position on 10 November 2026 is this. We found no page for it in Anthropic's connector directory on 10 November 2026. The MariaDB MCP server is listed in the MCP Registry as com.mariadb/mariadb-docs, which is a different thing from a Claude connector, and the registry describes it as: "Search and read the official MariaDB documentation for every MariaDB product, plus release notes."

This is the registry entry as read on 10 November 2026. We have not run it and make no claim about it.

The description mentions only searching and reading MariaDB documentation and says nothing about connecting to your database.

Next step: Kriv AI's agentic AI and automation service covers putting Claude on your own data with written rules and a person accountable. See the agentic AI and automation page.

Sources: MCP Registry, com.mariadb/mariadb-docs (https://registry.modelcontextprotocol.io/v0/servers?search=mariadb), read 10 November 2026.

A Claude Plotly Cloud integration is a connector made by Plotly. Its directory page says it will "Build and deploy Plotly Dash apps to Plotly Cloud from a conversation with Claude." It shows an Anthropic verified badge, was added in August 2026, shows no beta label and requires sign-in. It lists nine tools: authenticate, create_app, delete_app, get_app_logs, get_app_status, get_app_thumbnail, list_apps, publish_app and stop_app, at https://cloud.plotly.com/_mcp.

Plotly's own Plotly Cloud page describes a hosting platform for publishing Dash apps, with managed hosting, sharing and access controls. That page does not mention Claude or MCP, so what we say about the connector rests on the directory page alone.

Who uses it: people who build Dash apps and want to publish them. That is our reading. Its tools can publish, stop and delete apps, not only read data.

Next step: decide who may connect it and who may publish or delete an app through Claude. See Claude training for teams.

Sources: Anthropic connector directory, Plotly Cloud (https://claude.com/connectors/plotly-cloud); Plotly Cloud (https://plotly.com/cloud/), read 10 November 2026.

Start with read-only access where the maker offers it, as ClickHouse does, and give each person the access they already have in the source tool, as Airtable and DataGrail describe. Keep sensitive data out of connectors you have not reviewed, and keep a person accountable for any connector that can change records.

Write down who reviews the answers Claude gives from your data before they are used in a decision.

Anthropic's directory pages carry the line "Only use connectors from developers you trust" and say Anthropic does not control which tools a developer makes available or verify that they work as intended.

This page covers seventeen tools. Others exist and are not covered here.

We could not read Consensus's own documentation page, and beehiiv's pages gave no requirements for the directory connector, so those sections rest mostly on the directory page. We tested none of these tools.