Claude Denodo connectorWhat Claude can do in your Denodo account.
The Claude Denodo connector exposes 6 tools, all 6 of them reads. 0 write tools, 0 left undocumented. Below: what Claude can see in your Virtual DataPort databases, why its queries stay SELECT-only, and what has to be running before you plug it in.
Verified Trustpilot reviews · AI, automation & growth agency
Why your data team would plug Denodo into Claude
You stop writing VQL by hand for every quick question, and you stop waiting on the one colleague who knows the views by heart. You ask Claude which views hold customer data, or what columns a view has, and it calls the Denodo tools itself, reads the answer and explains it in plain English.
Find your way around an unfamiliar database. A new analyst asks what lives in the sales database. get_view_names lists every view, then get_view_schema opens the one that looks right and shows its columns and their types.
Get an answer, not a query. Someone in finance wants totals by region. Claude drafts the VQL query, can check it first with validate_vql_query, then runs it through run_vql_query and summarizes the rows it gets back.
Open only what you chose to share. Tag a view with mcp in Denodo and it appears as its own tool, named after the database and the view. Claude queries that view directly, without touching the rest.
Now what it will not do. Denodo's own changelog says the query tools are SELECT-only: inserts, updates, deletes and schema changes are blocked on the Denodo side. Claude also needs a Denodo MCP Server that someone in your team already runs, and the extension lives in Claude Desktop only. Nothing runs on its own either: no tool wakes up when a view changes. For scheduled jobs that watch your data, an automation tool is a different job; our Integrations hub gathers that side.
Five words before you start
The vocabulary you will meet while installing Denodo in Claude.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs on its own, and the directory lists them by name.
- Authorization
- The sign-in step of the service itself, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Denodo.
Plug Denodo into Claude in three steps
- 01
Find Denodo in Claude
In Claude's settings, open Customize, then Connectors, and look for Denodo in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before members can sign in to it.
- 02
Start the connection
Click Connect on its row, then sign in to Denodo in the window that Denodo opens. The extension offers several sign-in modes, including a username and password or a browser login. If the link breaks later, Disconnect and plug it back in.
- 03
Read the authorization screen
Read the sign-in screen before you confirm. It belongs to the service, not to Claude, and it decides what the access covers. You can also withdraw that access later from the Denodo side.
The 6 tools, grouped by what they do
Denodo MCP Connector gives Claude 6 tools: 6 that read your account, 0 that change something in it.
All six read. Tool names stay exactly as Claude shows them, in English.
- 6 read
What Claude reads (6)
6 toolsSix tools that look at your Denodo databases without changing them.
get_database_schema
Pulls the full schema of the database you connected: the whole structure of the database in one answer.
get_view_names
Returns the list of every view name in the database. A table of contents of the database, nothing opened yet.
get_view_schema
Opens one specific view and gives back its columns and their types. Nothing in the view's data is returned, only its structure.
run_vql_query
Executes a VQL query against the database and brings the rows back into the chat for Claude to read and summarize.
validate_vql_query
Checks that a VQL query is valid without running it. Claude can catch a syntax mistake before anything hits the database.
<database_name>_query_<tagged_view_name>
A family of tools rather than one: every view tagged mcp in Denodo becomes its own query tool, named after its database and the view itself.
What Claude asks you before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, keeping reads open and closing writes, and nobody overrides that from their own account. Claude also works with your rights and nothing more: a view your Denodo user cannot query stays closed to Claude too. The official per-tool labeling (read-only versus write and delete) lives only in the settings of a connected account; no public page publishes it.
Which plans it works on
Out of 819 sheets in the official directory, 0 shows plan availability. The connector-by-connector answer is published nowhere: it is a real gap in the catalog, not something we missed.
The general rule is published. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install in Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organization before each member can connect. For the current state, check the Denodo sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a view is refreshed or a source goes stale.
Only Denodo documents this connector; no Claude help page covers it. A tool list that shows only reads is an observed floor, not a guarantee: an administrator can open actions that appear on no public sheet. The partner badge in the directory is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not vouch for how they behave. Plug in what comes from a publisher you trust. Every connector in the directory gets its own page on our site, the Claude affinity connector for example.
Need help connecting Denodo MCP Connector to Claude?
A person reads every message.
