Ultipa

Manage Ultipa Cloud instances and run GQL graph queries, algorithms, backups, and metrics from Claude.

Category: Developer Tools
Primary Subcategory: Self-Serve BI & Conversational Analytics

Integration details

Description

Model Context Protocol server for Ultipa Cloud and any self-managed Ultipa GQLDB instance. Provision and operate instances, run GQL queries and graph algorithms, manage backups and firewall rules, and view metrics and billing — all through natural language.

Integration type: Connector
Verification status: Verified connector
Platform: Claude
Category: Developer Tools
Primary Subcategory: Self-Serve BI & Conversational Analytics
Secondary Subcategories: None listed
Brand: Ultipa
Access: Unknown
First tracked: 2026-06-21
Tool count: 57
Geography: US

Claude Discoverability Score

Ultipa isn’t discoverable through Claude’s Connector picker

It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.

No spam. Unsubscribe any time.

What the current score measures

Claude showing a list of relevant Connectors in a conversation

Remote Connectors Claude can surface from the Connector picker.

How this score is measured

Primary Subcategory

Self-Serve BI & Conversational Analytics

View Category

Adobe Customer Journey Analytics10/100

Adzviser ActiveCampaignPending VerificationGet notified

Adzviser Amazon Seller CentralPending VerificationGet notified

Adzviser BigCommercePending VerificationGet notified

Adzviser CallRailPending VerificationGet notified

—UltipaLocal Extension · Not scored

Tools

57 tools agents can invoke

Add a CIDR to the allowlist.
Remove the schedule (existing backups kept).
Trigger an on-demand backup (default 10-min timeout).
Create a new graph (OPEN / CLOSED / ONTOLOGY).
Provision a new instance (name, region, sizeId).
Permanently delete a specific backup from an instance. Synchronous. Requires `instances:delete` scope on the API key. Does NOT affect the instance itself — only removes the backup
Drop a graph.
Delete an instance. Requires the instance name as confirmation.
Detect graph mode (OPEN / CLOSED / ONTOLOGY) and run schema introspection.
Return the execution plan without running the query.
Authenticated account profile (email, name, balance flags).
Current auto-reload settings.
Current account balance and billing flags.
GQLDB Edition + license info.
Live GQLDB version reported by the instance.
Enterprise-tier eligibility. Pre-check before creating an enterprise instance.
Fetch one instance by ID.
Fetch admin username and password of the instance.
Recent container logs (default 100 lines, max 1000).
Latest available GQLDB version.
Current CPU / memory / disk / network snapshot.
Historical metrics over the last N minutes (default 60, max 14 days).
Public IP of the machine running Ultipa MCP (pair with `add_firewall_rule` to allow `${ip}/32`).
Whether instance ops are globally locked (maintenance / freeze).
Saved card info.
Free-trial eligibility. Pre-check before creating a free-trial instance.
Monthly usage-based billing summary.
Bulk-write structured nodes / edges via the driver's gRPC bulk-insert path. Highly recommend to provide filepath to the CSV, JSON, or JSONL files.
All alerts across the account's instances.
List backups for an instance.
List deleted instances (not returned by `list_instances`).
IP-allowlist rules for an instance.
List all graphs on the instance.
Alerts for a single instance.
List available sizes and pricing.
List all instances on the account.
List supported regions and their Manager URLs.
Balance transactions (top-ups, charges, refunds).
Fetch one documentation page's full content by exact path. Useful for the agent to ground GQLDB features and GQL composition in authoritative reference.
Pause a running instance.
Rebuild the instance's stored statistics.
Remove a rule by its CIDR.
Change an instance's display name.
Rotate the admin DB password. Breaks existing connections.
Restart the instance.
Restore from a completed backup. **Destructive: overwrites current data.**
Resume a paused instance.
Run a built-in graph algorithm. Centrality, community detection, similarity, pathfinding, graph embeddings, etc. Same execution as `run_gql_query`; separate so the agent surfaces the algorithm catalog for analytical questions.
Execute a GQL query and return results.
Search the Ultipa documentation by keyword or question. Returns ranked pages, each with a `topic` to pass to `lookup_docs`.

Ultipa FAQ

How do I improve a Verified connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.