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
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.
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.
Install the Claude Ultipa connector
- 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.
- 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.
- 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.
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
Tools index
- get_account
- list_instances
- list_deleted_instances
- get_instance
- get_instance_credentials
- list_regions
- list_instance_sizes
- get_enterprise_status
- get_operations_lock
- get_trial_status
- get_latest_version
- wait_for_instance_status
- get_live_metrics
- get_metrics_history
- get_instance_logs
- list_alerts
- list_instance_alerts
- get_my_ip
- list_firewall_rules
- get_balance
- list_transactions
- get_usage
- get_payment_method
- get_auto_reload
- list_backups
- test_connection
- explain_query
- run_algo
- list_graphs
- describe_schema
- get_db_version
- get_db_license
- search_docs
- lookup_docs
- create_instance
- rename_instance
- pause_instance
- resume_instance
- restart_instance
- upgrade_version
- delete_instance
- reset_admin_password
- set_log_level
- add_firewall_rule
- remove_firewall_rule
- create_backup
- restore_backup
- set_backup_schedule
- delete_backup
- clear_backup_schedule
- create_graph
- delete_graph
- write_data
- import_data
- write_procedure
- reload_db_stats
What Claude reads (34)
34 toolsget_account
Returns the connected Ultipa Cloud account's profile: email address, name and balance-related flags.
list_instances
Lists every instance attached to the account, so you know what is running before you act on anything.
list_deleted_instances
Shows the instances already removed from the account, which no longer appear in the regular list of instances.
get_instance
Fetches the record of one specific instance from its ID, so its state and characteristics can be checked.
get_instance_credentials
Retrieves an instance's admin username and password as Ultipa Cloud stores them.
list_regions
Lists the regions where Ultipa Cloud can host an instance, along with the address of their management console.
list_instance_sizes
Presents the instance sizes on offer and their pricing, so options can be compared before provisioning one.
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.
get_operations_lock
Reports whether instance operations are locked across the whole service, during maintenance or a freeze for example.
get_trial_status
Checks whether the account can still open a trial instance; Ultipa makes it a pre-check before that kind of instance.
get_latest_version
Gives the most recent version of GQLDB, Ultipa's graph database engine, available at the time you ask.
wait_for_instance_status
An explicit polling helper that keeps checking an instance's state; Ultipa notes it is rarely needed.
get_live_metrics
Takes a snapshot of an instance's resources: CPU, memory, disk and network, at the moment you ask.
get_metrics_history
Pulls historical metrics over the last minutes you ask for: 60 by default, up to 14 days at most.
get_instance_logs
Shows an instance's recent container logs, the raw output of the server: 100 lines by default, 1000 at most.
list_alerts
Gathers the alerts from every instance on the account into a single view.
list_instance_alerts
Keeps only the alerts for a single instance, to focus on the one causing trouble.
get_my_ip
Gives the public IP address of the machine running Ultipa's server, to pair afterwards with a firewall rule.
list_firewall_rules
Displays an instance's IP allowlist, in other words who is allowed to connect to it.
get_balance
Reports the Ultipa Cloud account's current balance and the related billing flags.
list_transactions
Lists balance movements: top-ups, charges and refunds.
get_usage
Summarizes the month's usage-based billing: what instance consumption has cost over the period.
get_payment_method
Shows the details of the card saved on the Ultipa Cloud account.
get_auto_reload
Displays the current auto-reload settings for the account balance.
list_backups
Enumerates an instance's existing backups, before deciding which one to restore or keep.
test_connection
Runs a quick health check on the target GQLDB instance to confirm it responds.
explain_query
Returns the execution plan of a GQL query without running it, to see how the engine would go about it.
run_algo
Runs a built-in graph algorithm: centrality, community detection, similarity, pathfinding, graph embeddings and more.
list_graphs
Enumerates the graphs present on the instance, to pick the one to work on.
describe_schema
Detects a graph's mode (open, closed or ontology) and inspects its schema, to learn which nodes and relationships it holds.
get_db_version
Gives the GQLDB version the instance reports about itself, live.
get_db_license
Reports the GQLDB edition and the license information for the instance.
search_docs
Searches Ultipa's documentation by keyword or question and returns ranked pages, each with a topic to open next.
lookup_docs
Fetches the full content of one documentation page from its exact path, to ground an answer in Ultipa's reference.
What Claude changes (22)
22 tools22 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 ruleStarts a new Ultipa Cloud instance with a name, a region and a size.
rename_instance
Approval: see the ruleChanges an instance's display name, without touching its data.
pause_instance
Approval: see the ruleSuspends a running instance.
resume_instance
Approval: see the ruleBrings a paused instance back so it answers queries again.
restart_instance
Approval: see the ruleRestarts the instance, the usual move when it stops behaving normally.
upgrade_version
Approval: see the ruleMoves the instance to the latest GQLDB version available.
delete_instance
Approval: see the ruleDeletes an instance from the account. Ultipa requires the instance's name as confirmation.
reset_admin_password
Approval: see the ruleReplaces the database's admin password with a new one.
set_log_level
Approval: see the ruleSets how detailed GQLDB's logs are: debug, info, warn or error.
add_firewall_rule
Approval: see the ruleAdds an IP range to an instance's allowlist so it can connect.
remove_firewall_rule
Approval: see the ruleRemoves a rule from the allowlist based on its IP range.
create_backup
Approval: see the ruleTriggers a one-off backup of an instance, with a default timeout of 10 minutes.
restore_backup
Approval: see the ruleReturns an instance to the state of a completed backup. Ultipa calls it destructive: current data is overwritten.
set_backup_schedule
Approval: see the ruleSets or adjusts an automated backup schedule for an instance.
delete_backup
Approval: see the rulePermanently deletes a backup snapshot.
clear_backup_schedule
Approval: see the ruleRemoves the automated backup schedule; backups already taken are kept.
create_graph
Approval: see the ruleCreates a new graph on the instance, in open, closed or ontology mode.
delete_graph
Approval: see the ruleDrops an entire graph from the instance.
write_data
Approval: see the ruleRuns a GQL data-manipulation statement that Claude composes itself. For a file on your machine, Ultipa points to bulk import instead.
import_data
Approval: see the ruleBulk-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.
write_procedure
Approval: see the ruleCreates a stored procedure on the instance, reusable afterwards.
reload_db_stats
Approval: see the ruleRebuilds the instance's stored statistics.
Unclassified (1)
1 toolUltipa 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.
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.
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.
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 connecting Ultipa to Claude?
A person reads every message.