Resources · Claude connector

Claude Ultipa connectorWhat Claude can do in your Ultipa account or instance.

The Claude Ultipa connector exposes 57 tools. 34 read your account, instances and graphs, 22 change something there, and 1 stays unclassified. Here: what Claude administers, what is destructive, how to install it and who can cut access.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes when you run a graph database

Ultipa offers GQLDB, a graph database, as a cloud service or installed on your own servers. With the connector, Claude checks instance health, queries graphs and, once you approve, acts on the infrastructure itself. Ultipa documents the whole set in the README of its official repository.

Diagnose a slow instance. get_live_metrics gives CPU, memory, disk and network right now, get_metrics_history the history up to 14 days, and get_instance_logs the recent logs.

Analyze a graph before touching it. Claude describes the schema with describe_schema, checks an execution plan with explain_query, then runs a centrality or community-detection algorithm with run_algo to surface the most connected or clustered nodes.

Protect data before a change. create_backup takes an on-demand backup, set_backup_schedule schedules more, and restore_backup rolls back, overwriting whatever happened since.

What Claude does not do: manage a self-managed instance from Claude on the web, or act on billing beyond reading it. Nothing runs on its own either: no alert wakes Claude up when an instance goes down. That kind of round-the-clock watch calls for an automation tool, a different trade; Integrations gathers that side.

Vocabulary

The vocabulary in one minute

Five words to follow the rest.

Connector
The link you set up once between Claude and a service, so it can work there while it answers you.
Tool
A named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory sheet lists them.
Authorization
What you hand Claude so it can act: here an Ultipa Cloud API key or an instance's credentials. You can withdraw it later.
Approval
The confirmation Claude waits for before an action that changes an account, shown in the chat right when it matters.
MCP
The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service.
Connect

Install the Claude Ultipa connector

  1. 01

    Open the directory in Claude Desktop

    The directory lists Ultipa as a desktop extension. In Claude Desktop, open Customize, then Connectors, and look for Ultipa in the directory, where its sheet lists all 57 tools.

  2. 02

    Install, then configure

    Search for Ultipa in the list, click Install, then Config. On a Team or Enterprise workspace, an Owner or Primary Owner must first have opened the connector to the organization.

  3. 03

    Enter your credentials

    Fill in either your Ultipa Cloud API key or the host, username and password of an instance you run yourself, then Save. What the key allows sets what Claude will be able to do.

Tools

The 57 tools, grouped by what they do

Ultipa gives Claude 57 tools: 34 that read your account, 22 that change something in it, and 1 no official source describes.

34 reading tools, 22 that modify, 1 unclassified. Tool names stay exactly as Claude shows them.

  • 34 read
  • 22 write
  • 1 not documented

What Claude reads (34)

34 tools

get_account

Returns the connected Ultipa Cloud account's profile: email address, name and balance-related flags.

When it helps
checking which Ultipa Cloud account Claude is working on before an action.
Watch out
it only answers for an Ultipa Cloud account, never for a self-managed instance connected directly.

Sourcegithub.com · October 1, 2026 ↗

list_instances

Lists every instance attached to the account, so you know what is running before you act on anything.

When it helps
seeing what exists on the account before acting on an instance.
Watch out
with an API key, Ultipa asks you to grant the instances:read scope for this kind of tool.

Sourcegithub.com · October 1, 2026 ↗

list_deleted_instances

Shows the instances already removed from the account, which no longer appear in the regular list of instances.

When it helps
you are looking for the trace of a database that vanished to understand what happened to it.
Watch out
list_instances does not return these instances, so this is the only tool on the sheet that shows them.

Sourcegithub.com · October 1, 2026 ↗

get_instance

Fetches the record of one specific instance from its ID, so its state and characteristics can be checked.

When it helps
before a maintenance task, you want to confirm you are looking at the right instance.
Watch out
it needs the instance ID, which the instance list provides first.

Sourcegithub.com · October 1, 2026 ↗

get_instance_credentials

Retrieves an instance's admin username and password as Ultipa Cloud stores them.

When it helps
when you need an Ultipa Cloud instance's admin credentials back.
Watch out
as a management tool it only works with Ultipa Cloud; with an API key, Ultipa files these credentials under the instances:credentials scope.

Sourcegithub.com · October 1, 2026 ↗

list_regions

Lists the regions where Ultipa Cloud can host an instance, along with the address of their management console.

When it helps
you need to host a database close to your users and want to see the options.
Watch out
this catalog belongs to Ultipa Cloud; a self-managed instance has no access to it.

Sourcegithub.com · October 1, 2026 ↗

list_instance_sizes

Presents the instance sizes on offer and their pricing, so options can be compared before provisioning one.

When it helps
you are drafting a budget and want to know what the next size up would cost.
Watch out
Ultipa counts it among the cloud management tools, so it does not answer for a directly connected instance.

Sourcegithub.com · October 1, 2026 ↗

get_enterprise_status

Tells whether the account qualifies for Ultipa's top business tier; Ultipa frames it as a pre-check before any instance at that tier is requested.

When it helps
before requesting an instance at that level, you want to know whether the account qualifies.
Watch out
like the trial check, it opens nothing by itself.

Sourcegithub.com · October 1, 2026 ↗

get_operations_lock

Reports whether instance operations are locked across the whole service, during maintenance or a freeze for example.

When it helps
an operation fails for no obvious reason and you want to rule out ongoing maintenance.
Watch out
it reports the lock without lifting it; no tool on the sheet acts on that lock.

Sourcegithub.com · October 1, 2026 ↗

get_trial_status

Checks whether the account can still open a trial instance; Ultipa makes it a pre-check before that kind of instance.

When it helps
you want to try Ultipa on a small dataset before committing a budget.
Watch out
it is only a check; Ultipa presents it as the step that comes before opening a free-trial instance, which is a separate tool.

Sourcegithub.com · October 1, 2026 ↗

get_latest_version

Gives the most recent version of GQLDB, Ultipa's graph database engine, available at the time you ask.

When it helps
you want to know whether your instance is behind before planning an upgrade.
Watch out
it speaks for Ultipa's catalog, not for the version actually running on your side.

Sourcegithub.com · October 1, 2026 ↗

wait_for_instance_status

An explicit polling helper that keeps checking an instance's state; Ultipa notes it is rarely needed.

When it helps
after asking Claude for a restart, you would rather it waits for the right state before the next step.
Watch out
it does not change the instance's state; it polls that state until it matches.

Sourcegithub.com · October 1, 2026 ↗

get_live_metrics

Takes a snapshot of an instance's resources: CPU, memory, disk and network, at the moment you ask.

When it helps
queries are slowing down and you want to see right away whether memory is maxed out.
Watch out
for a trend, get_metrics_history goes back up to 14 days.

Sourcegithub.com · October 1, 2026 ↗

get_metrics_history

Pulls historical metrics over the last minutes you ask for: 60 by default, up to 14 days at most.

When it helps
placing a load spike within an instance's recent history.
Watch out
for the state right now, get_live_metrics is the one to use.

Sourcegithub.com · October 1, 2026 ↗

get_instance_logs

Shows an instance's recent container logs, the raw output of the server: 100 lines by default, 1000 at most.

When it helps
a query fails with a vague message and you want the exact server-side trace.
Watch out
these are the container's recent logs; their level of detail depends on the setting applied through set_log_level.

Sourcegithub.com · October 1, 2026 ↗

list_alerts

Gathers the alerts from every instance on the account into a single view.

When it helps
you want an overall picture of incidents without opening each instance one by one.
Watch out
for a single instance, list_instance_alerts narrows the view.

Sourcegithub.com · October 1, 2026 ↗

list_instance_alerts

Keeps only the alerts for a single instance, to focus on the one causing trouble.

When it helps
focusing on the one instance that raises alerts while leaving the rest of the account aside.
Watch out
the account-wide view goes through list_alerts instead.

Sourcegithub.com · October 1, 2026 ↗

get_my_ip

Gives the public IP address of the machine running Ultipa's server, to pair afterwards with a firewall rule.

When it helps
your database refuses connections from your machine and you need to know which address to allow.
Watch out
the address is that of the machine running Ultipa's server, not necessarily your browser's.

Sourcegithub.com · October 1, 2026 ↗

list_firewall_rules

Displays an instance's IP allowlist, in other words who is allowed to connect to it.

When it helps
checking which addresses an instance currently admits.
Watch out
in API-key mode, Ultipa ties the read tools for instances to the instances:read scope.

Sourcegithub.com · October 1, 2026 ↗

get_balance

Reports the Ultipa Cloud account's current balance and the related billing flags.

When it helps
before launching one more instance, you want to check there is credit left.
Watch out
billing tools need the billing:read scope when you connect with an API key.

Sourcegithub.com · October 1, 2026 ↗

list_transactions

Lists balance movements: top-ups, charges and refunds.

When it helps
tracing a specific charge or top-up on the balance.
Watch out
with an API key, billing sits under the billing:read scope, just like the balance and the monthly usage summary.

Sourcegithub.com · October 1, 2026 ↗

get_usage

Summarizes the month's usage-based billing: what instance consumption has cost over the period.

When it helps
at month end, you want to know what consumption has added up to.
Watch out
in API-key mode, this summary also depends on the billing:read scope.

Sourcegithub.com · October 1, 2026 ↗

get_payment_method

Shows the details of the card saved on the Ultipa Cloud account.

When it helps
a payment was declined and you want to see which card is on file.
Watch out
it only displays the saved card; nothing on the sheet touches the payment method.

Sourcegithub.com · October 1, 2026 ↗

get_auto_reload

Displays the current auto-reload settings for the account balance.

When it helps
you want to know whether the account tops itself up or could run dry.
Watch out
it only displays the setting; the sheet publishes no tool that acts on it.

Sourcegithub.com · October 1, 2026 ↗

list_backups

Enumerates an instance's existing backups, before deciding which one to restore or keep.

When it helps
before a migration, you want to know the most recent backup available.
Watch out
a restore overwrites current data, so note the date carefully before going further.

Sourcegithub.com · October 1, 2026 ↗

test_connection

Runs a quick health check on the target GQLDB instance to confirm it responds.

When it helps
right after setup, you want to be sure Claude can actually reach your database.
Watch out
it only checks that the targeted GQLDB instance answers, and leaves it as it is.

Sourcegithub.com · October 1, 2026 ↗

explain_query

Returns the execution plan of a GQL query without running it, to see how the engine would go about it.

When it helps
a query takes too long and you want to see where it gets stuck.
Watch out
nothing is executed, which makes it the right reflex before a heavy query on production.

Sourcegithub.com · October 1, 2026 ↗

run_algo

Runs a built-in graph algorithm: centrality, community detection, similarity, pathfinding, graph embeddings and more.

When it helps
applying one of those algorithms to a graph already loaded on the instance.
Watch out
free-form GQL queries go through a different tool, run_gql_query, which stays unclassified.

Sourcegithub.com · October 1, 2026 ↗

list_graphs

Enumerates the graphs present on the instance, to pick the one to work on.

When it helps
you no longer remember the exact name of the test graph.
Watch out
it works on Ultipa Cloud as well as on a self-managed instance connected directly.

Sourcegithub.com · October 1, 2026 ↗

describe_schema

Detects a graph's mode (open, closed or ontology) and inspects its schema, to learn which nodes and relationships it holds.

When it helps
before tackling a complex question, Claude needs to understand the graph's structure.
Watch out
the three modes Ultipa names, open, closed and ontology, are also the ones create_graph uses.

Sourcegithub.com · October 1, 2026 ↗

get_db_version

Gives the GQLDB version the instance reports about itself, live.

When it helps
you are comparing it with the latest release to decide whether an upgrade is due.
Watch out
this is the version as the instance sees it, which may differ from the latest release.

Sourcegithub.com · October 1, 2026 ↗

get_db_license

Reports the GQLDB edition and the license information for the instance.

When it helps
when you need to know which edition and license cover an instance.
Watch out
the information comes live from the instance, not from the Ultipa Cloud account.

Sourcegithub.com · October 1, 2026 ↗

search_docs

Searches Ultipa's documentation by keyword or question and returns ranked pages, each with a topic to open next.

When it helps
you want the official syntax of a GQL function rather than an approximation.
Watch out
it searches Ultipa's documentation, not your graphs or your instances.

Sourcegithub.com · October 1, 2026 ↗

lookup_docs

Fetches the full content of one documentation page from its exact path, to ground an answer in Ultipa's reference.

When it helps
Claude needs to check an option before suggesting a query to you.
Watch out
it needs the page's exact path, which search_docs supplies.

Sourcegithub.com · October 1, 2026 ↗

What Claude changes (22)

22 tools

22 tools that act on your account, instances or graphs. No source spells out a confirmation on Claude's side, so the general rule applies.

create_instance

Approval: see the rule

Starts a new Ultipa Cloud instance with a name, a region and a size.

What Claude asks for
no source describes a confirmation specific to this tool; the general approvals rule applies.
When it helps
a new project needs its own graph database, kept apart from production.

Sourcegithub.com · October 1, 2026 ↗

rename_instance

Approval: see the rule

Changes an instance's display name, without touching its data.

What Claude asks for
the general approvals rule covers it, as no source gives it a confirmation of its own.
When it helps
the test instance has turned into a real project's database and its name is confusing.

Sourcegithub.com · October 1, 2026 ↗

pause_instance

Approval: see the rule

Suspends a running instance.

What Claude asks for
nothing is described for it in particular, so the default confirmation is what applies.
When it helps
when an instance does not need to run for a while.
Watch out
resume_instance is the tool that brings a paused instance back afterward.

Sourcegithub.com · October 1, 2026 ↗

resume_instance

Approval: see the rule

Brings a paused instance back so it answers queries again.

What Claude asks for
Ultipa documents no specific prompt; Claude's default rule holds here.
When it helps
when a paused instance needs to serve again.
Watch out
with an API key, state changes like this one need the instances:write scope.

Sourcegithub.com · October 1, 2026 ↗

restart_instance

Approval: see the rule

Restarts the instance, the usual move when it stops behaving normally.

What Claude asks for
no confirmation of its own in the sources, so the general rule below.
When it helps
an instance no longer responds properly after a settings change.

Sourcegithub.com · October 1, 2026 ↗

upgrade_version

Approval: see the rule

Moves the instance to the latest GQLDB version available.

What Claude asks for
no particular prompt is sourced; refer to the general approvals rule.
When it helps
when get_latest_version reports a newer version than the instance runs.
Watch out
Ultipa does not describe a rollback after the upgrade.

Sourcegithub.com · October 1, 2026 ↗

delete_instance

Approval: see the rule

Deletes an instance from the account. Ultipa requires the instance's name as confirmation.

What Claude asks for
Claude's default confirmation, since no source describes a rule of its own.
When it helps
a temporary test environment no longer has any reason to exist.
Watch out
this is the heaviest operation on the list, so reread the name before confirming it.

Sourcegithub.com · October 1, 2026 ↗

reset_admin_password

Approval: see the rule

Replaces the database's admin password with a new one.

What Claude asks for
the sources are silent on a dedicated prompt, so the general rule takes over.
When it helps
when the current admin password should stop working.
Watch out
Ultipa warns that this breaks existing connections.

Sourcegithub.com · October 1, 2026 ↗

set_log_level

Approval: see the rule

Sets how detailed GQLDB's logs are: debug, info, warn or error.

What Claude asks for
no specific rule is published, so the default confirmation covers it too.
When it helps
to diagnose an anomaly, you want more verbose logs for a while.

Sourcegithub.com · October 1, 2026 ↗

add_firewall_rule

Approval: see the rule

Adds an IP range to an instance's allowlist so it can connect.

What Claude asks for
the shared approvals rule, since nothing specific to this tool is described.
When it helps
when a new address must be able to reach the instance, such as the public address the dedicated tool returns.

Sourcegithub.com · October 1, 2026 ↗

remove_firewall_rule

Approval: see the rule

Removes a rule from the allowlist based on its IP range.

What Claude asks for
with no description of its own, Claude's default rule frames the call.
When it helps
when an address range should no longer reach the instance.
Watch out
the rule is identified by its IP range, so have it at hand.

Sourcegithub.com · October 1, 2026 ↗

create_backup

Approval: see the rule

Triggers a one-off backup of an instance, with a default timeout of 10 minutes.

What Claude asks for
no source spells out a confirmation for it; see the general rule.
When it helps
right before a large import, you want a restore point.

Sourcegithub.com · October 1, 2026 ↗

restore_backup

Approval: see the rule

Returns an instance to the state of a completed backup. Ultipa calls it destructive: current data is overwritten.

What Claude asks for
nothing specific in the sources; Claude's default approval stays the reference.
When it helps
a botched import damaged the graph and you need to go back to the day before.
Watch out
everything added since the backup is lost.

Sourcegithub.com · October 1, 2026 ↗

set_backup_schedule

Approval: see the rule

Sets or adjusts an automated backup schedule for an instance.

What Claude asks for
the same general rule as the other write tools, as no source says otherwise.
When it helps
the database is going into production and must be backed up without anyone thinking about it.

Sourcegithub.com · October 1, 2026 ↗

delete_backup

Approval: see the rule

Permanently deletes a backup snapshot.

What Claude asks for
no behavior documented for it alone, so the default confirmation stands.
When it helps
old backups clutter the list and serve no purpose anymore.
Watch out
no way back is described after this deletion.

Sourcegithub.com · October 1, 2026 ↗

clear_backup_schedule

Approval: see the rule

Removes the automated backup schedule; backups already taken are kept.

What Claude asks for
Claude's general confirmation, as no source describes one for this tool.
When it helps
an archived database no longer needs regular backups.
Watch out
from then on, no new backup happens unless someone asks for one.

Sourcegithub.com · October 1, 2026 ↗

create_graph

Approval: see the rule

Creates a new graph on the instance, in open, closed or ontology mode.

What Claude asks for
the default rule, since nothing particular is documented for this action.
When it helps
you want a separate space to test a data model without touching the main graph.

Sourcegithub.com · October 1, 2026 ↗

delete_graph

Approval: see the rule

Drops an entire graph from the instance.

What Claude asks for
no specific confirmation on record; the general rule frames it.
When it helps
a trial graph has served its purpose and needs to go.
Watch out
everything inside the graph goes with it.

Sourcegithub.com · October 1, 2026 ↗

write_data

Approval: see the rule

Runs a GQL data-manipulation statement that Claude composes itself. For a file on your machine, Ultipa points to bulk import instead.

What Claude asks for
the general rule, absent any source describing a dedicated confirmation.
When it helps
you want to fix a few relationships entered wrongly in the graph.

Sourcegithub.com · October 1, 2026 ↗

import_data

Approval: see the rule

Bulk-writes structured nodes and edges through the driver's bulk-insert path. Ultipa points to it, rather than write_data, for files on your machine.

What Claude asks for
the sources say nothing beyond the general approvals rule.
When it helps
when the data to load sits in a local file whose path you provide.

Sourcegithub.com · October 1, 2026 ↗

write_procedure

Approval: see the rule

Creates a stored procedure on the instance, reusable afterwards.

What Claude asks for
nothing is published about a dedicated prompt, so the default confirmation applies.
When it helps
a set of queries needs to be grouped under one name.
Watch out
no tool on the sheet deletes a stored procedure once it exists.

Sourcegithub.com · October 1, 2026 ↗

reload_db_stats

Approval: see the rule

Rebuilds the instance's stored statistics.

What Claude asks for
the default confirmation, as no source details what Claude asks here.
When it helps
after a large import, you want the statistics to reflect the new data.
Watch out
this one writes to the instance, unlike get_db_version and get_db_license, which only read.

Sourcegithub.com · October 1, 2026 ↗

Unclassified (1)

1 tool

Ultipa describes this tool, but no source says whether it reads or modifies: that depends on the query.

run_gql_query

Executes a GQL query and returns the results, per Ultipa's README. No source says whether the tool reads or modifies: it depends on the query, and the sheet does not settle it.

Watch out
the general approvals rule covers it.
Approvals

What Claude asks before it acts

By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the chat when it applies.

No source describes a confirmation specific to any Ultipa tool on Claude's side, so the default rule covers the 22 tools that modify. On Ultipa's side, deleting an instance also requires its name. With an API key, the scopes granted to that key bound Claude as well. On a Team or Enterprise workspace, owners decide whether a member may let some actions through, and they can close writing for the whole organization.

Plans

Which plans it is available on

None of the 819 sheets in the official directory shows plan availability. That answer, connector by connector, is not published anywhere.

The general rule is published: desktop extensions such as Ultipa install on Claude Desktop for all users, and remote connectors are open on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members connect. The current state is on the connector's sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation: Claude calls these tools while it answers you, and nothing fires on its own. Only Ultipa documents this connector, in the README of its official repository.

Several tools touch infrastructure and production data: restoring, deleting, rotating a password. The directory badge is not a security audit, and Anthropic says so on every sheet: it does not choose a publisher's tools and does not guarantee how they behave. Connect what comes from a publisher you know, read each destructive request twice, and for monitoring that runs without you, see Integrations.

Need help

Need help connecting Ultipa to Claude?

A person reads every message.

FAQ

Claude Ultipa connector: common questions

01What can Claude do with the Claude Ultipa connector?
Claude can administer your Ultipa Cloud instances and query your graphs from the chat. On the management side, it checks the account, instances, metrics, logs, alerts, firewall, backups and billing, and it can provision, pause, restart or delete an instance. On the data side, it describes a schema, explains a query, runs a graph algorithm or imports data. Two more tools search and read Ultipa's documentation, so answers can rest on the official reference.
02Can Claude delete data or an instance?
Yes, several tools allow it: deleting an instance, a backup or a whole graph, restoring a backup over current data, or rotating the admin password and breaking connections. Ultipa adds a safeguard on instance deletion, which requires the instance name as confirmation. With an API key, these actions also depend on the scopes granted, the delete scope included. Read every request carefully before approving, especially on a production database where mistakes are costly.
03Does Claude ask before it acts?
By default, yes: Claude asks for confirmation before every action it takes on an account for you. No source describes a confirmation specific to Ultipa's tools on Claude's side, so that general rule covers the 22 tools that modify. The GQL query tool remains unclassified, and the same rule covers it. On Team and Enterprise, owners can shut writing off for the whole organization, and members cannot work around it.
04Which plans is it available on?
No official source publishes plan availability connector by connector, and no directory sheet displays it. The general rule says desktop extensions such as Ultipa install on Claude Desktop for all users. On Team and Enterprise, an Owner or Primary Owner first opens the connector to the organization. For the current state of your own account, check the connector's sheet in the official directory, which tracks changes as they come and reflects them there first.
05Does Claude see my whole Ultipa account?
It sees what the credentials you provide open to it, and nothing more. With an Ultipa Cloud API key, each family of tools depends on a scope: read, write, delete, credentials or billing. With the web connection, each person signs in to their own account and only sees their own instances. Ultipa also states that its server reads neither your chats nor your files, except the file paths you explicitly pass to the import tool.
06Can I connect an Ultipa instance I host myself?
Yes, but not from Claude on the web, whatever your settings there. Ultipa explains that a self-managed instance connects through Claude Desktop or a local client, with its host, username and password. In that mode, only the data-side tools work: queries, schema, algorithms, import and procedures. The tools for managing the account, backups or billing require Ultipa Cloud, and a direct instance cannot use them at all, whichever Claude app you open.
07Claude or an automation tool for Ultipa?
They do different jobs, so it depends on the use. The connector fits a question or a request made in a chat: why this instance is slow, what this algorithm returns, back up before the import. It launches nothing by itself and does not react to an alert. An automation tool runs steps without you, starting from an event. The two complement each other more than they replace one another.