Cloudcrane
CloudCrane curates catalog data for AI products. Rules settle what they can, a model may only choose from the values you allowed, anything it is unsure of waits for a person, and every value keeps a receipt saying how it was decided. This connector lets Claude work in your CloudCrane workspace. Reading (17 tools, always available): list datasets and their fields, read field contracts and value definitions, check what is blocking a release, triage the review queue, see the receipt behind any value, follow runs, deployed tools, scenarios, drift alerts, usage, approval requests and events. Building (13 tools, only if the workspace owner allows it when connecting): create datasets, fields and value sets, start runs, publish a release when the accuracy gate passes by itself, deploy a tool and create its keys, add and run scenarios, and ask a person for approval. Each of these changes data, so Claude asks you before every call. What no connection can do: decide a review item, edit a stored value, delete anything, remove a value from a safety field, or publish past the accuracy gate. Those stay with a person, because a receipt names who decided; Claude can only file an approval request. Sign in with your CloudCrane account. A workspace owner picks the workspace and whether Claude may read only or also build. Imported record contents stay hidden unless the owner turns them on. Free to sign up; every plan includes the connector.
Choose a connection option
17 tool names reported
Source-declared tools. Availability can depend on the connection and permissions; these are not runtime test results.
Claude connector directory ↗ · Observed 2026-11-01 · Completeness not established
get_approvalget_datasetget_next_actionsget_readinessget_receiptsget_runget_tool_insightsget_usagelist_approvalslist_contractslist_datasetslist_drift_alertslist_eventslist_review_itemslist_scenarioslist_toolslist_value_sets
Sources and provenance
- Claude connector directoryClaude tier: community · Observed
- Official MCP RegistryObserved
Grouping basis: endpoint. Exact endpoints or package sets can be grouped automatically; other relationships require evidence review. This does not verify publisher affiliation, connection health, or equivalent capabilities.