Claude Valuecase App connectorWhat Claude can do in your Valuecase App account.
The Claude Valuecase App connector exposes 35 tools. 12 read your spaces, templates and comments, 16 build or change them, and 7 carry no description anywhere. Here: what Claude does in your sales rooms, what it asks, and where it stops.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Valuecase App
Valuecase hosts the digital sales rooms and onboarding spaces you share with customers. With the connector, you stop clicking through each space before a pipeline review or rebuilding a room by hand after a call. You ask Claude, it reads the spaces, plans and comments, and it can personalise a space or spin up a new one from a template.
A pipeline review in one question. list_spaces filters your active rooms, list_space_action_plans shows which customer tasks are overdue, and update_task_dates resets them once the customer agrees.
A meeting transcript turned into a tailored room. Hand Claude the notes: get_space_content_tree finds the welcome text and next steps, add_or_edit_content_items updates them, and insert_asset_library_item adds the implementation guide from your library.
A new customer, set up properly. get_template_space_properties checks which fields a template requires, Claude asks you for what is missing, then create_space builds the room.
Now what it does not do. It can archive a space but never permanently delete one. Workflows, branding, integrations, property definitions and sharing settings stay in the Valuecase interface, and a brand-new file must be uploaded to the Asset Library before Claude can use it. Nothing runs by itself either: no tool fires when a buyer opens a room. For that kind of background job, see the Valuecase App Make integration.
The vocabulary in one minute
Five words you will meet while plugging Valuecase in.
- Connector
- The link you set up once between Claude and an account you already have, so it can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, 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 in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Valuecase.
Plug Valuecase App into Claude in three steps
- 01
Find Valuecase App in Claude
In Claude's settings, open Customize, then Connectors, and look for Valuecase App in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, then each member connects on their own.
- 02
Start the connection
Click Connect on its row and sign in to Valuecase in the window Valuecase opens itself. If the link breaks later, use Disconnect and plug it back in from the same row.
- 03
Read the authorization screen
Read the permissions screen before you accept. It belongs to Valuecase, not to Claude, and it sets what the access covers. You can withdraw that access later from your Valuecase account too.
The 35 Claude Valuecase App connector tools, grouped by what they do
Valuecase App gives Claude 35 tools: 12 that read your account, 16 that change something in it, and 7 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. The names stay exactly as Claude shows them.
- 12 read
- 16 write
- 7 not documented
What Claude reads (12)
12 toolsTools that look at spaces, templates, plans, properties, forms and comments without touching them.
get_block
It belongs to the three reading tools behind what Valuecase calls reviewing a space's content. Valuecase lists this capability without detailing what each of its three reading tools returns.
get_content_outline
Another of the three tools Valuecase ties to reviewing what a space contains, with no sentence of its own.
get_space_content_tree
The third tool Valuecase groups under reviewing a space's content; like the other two, its exact output goes undescribed.
get_template
Reviews the content of one template, the model new spaces start from, so Claude can judge whether it fits a use case.
get_template_space_properties
Checks which properties a template requires before a space can be created from it, so Claude asks you for anything missing first.
list_space_action_plans
Reviews the action plans of a space and their tasks, so overdue items stand out.
list_space_comments
Reads the comments posted in a space, where customers and your team discuss the deal.
list_space_form_submissions
Accesses what customers submitted through the forms in a space, such as intake questionnaires.
list_space_properties
Shows the properties of a space, both space properties and internal properties, the two kinds Valuecase names.
list_spaces
Searches and filters your spaces, the digital sales rooms and onboarding spaces you share with customers.
list_templates
Lists the templates available in your workspace, so Claude can suggest one that fits the space you need.
search_asset_library
Searches your Asset Library, the shared stock of files and content your team reuses across spaces.
What Claude changes (16)
16 toolsTools that create, edit, reorder, remove, archive or comment. No source gives any of them its own confirmation rule: the general rule below applies.
add_or_edit_content_items
Approval: see the ruleOne of the two tools Valuecase ties to editing existing text, links, action plans, Gantt charts, form questions and other supported blocks. Valuecase does not spell out how it differs from edit_content_item.
add_space_stakeholder
Approval: see the ruleAdds or invites a stakeholder to a space, so a new person on the customer side gets access to the room.
archive_space
Approval: see the ruleArchives a space. Valuecase is explicit that the connector can archive but never permanently delete a whole space.
create_block
Approval: see the ruleAdds a content block inside a page of a space, the building piece Valuecase names when it says the assistant can create pages and add blocks.
create_page
Approval: see the ruleCreates a new page in a space, the container blocks then go into.
create_space
Approval: see the ruleSpins up a new space from a template, the personalised room a customer will open.
create_space_comment
Approval: see the ruleAdds a comment or replies in a space, with real @mentions: a mentioned person gets the same notification as a mention made in Valuecase itself.
delete_content_items
Approval: see the ruleRemoves selected content such as pages or blocks from a space. Valuecase draws the line there: content goes, a whole space never does.
edit_content_item
Approval: see the ruleEdits existing content, text, a link, an action plan or a form question: the other tool Valuecase attaches to content editing, with no word on how it differs from add_or_edit_content_items.
insert_asset_library_item
Approval: see the ruleAdds an item that already sits in your Asset Library to a space, such as a case study or a guide.
reorder_content_items
Approval: see the ruleReorders pages, blocks and items, so a space reads in the order the conversation with the customer now follows.
set_content_visibility_rule
Approval: see the ruleSets whether supported content is shown or hidden, and in templates sets visibility rules based on supported properties.
set_task_completion
Approval: see the ruleMarks tasks of an action plan as completed, so the action plan reflects what is actually done.
update_space_internal_property
Approval: see the ruleUpdates an internal property of a space, the second kind Valuecase names next to space properties.
update_space_property
Approval: see the ruleChanges a space property, such as a go-live date recorded on the space.
update_task_dates
Approval: see the ruleChanges the due dates of action plan tasks, a change Valuecase lists next to marking tasks completed.
Undocumented (7)
7 toolsThe directory publishes these names and nothing more. Valuecase describes capabilities without naming them, and the page does not guess.
get_block_types
Valuecase's article describes capabilities, not this name, and no official source documents it anywhere. Guessing its role from the wording would be inventing, so the note stops here.
get_content_editing_guide
Nothing official ties this entry to any sentence: Valuecase's help page never names it, and Claude publishes no page for this connector. It remains a bare name on the directory sheet.
get_space_summary
Valuecase mentions reviewing engagement and recent activity, but no source ties that sentence to this name, and no documentation describes it. The page does not make the link itself.
get_visibility_options
Only the directory lists this name. Valuecase documents visibility as a capability tied to another tool, and no source describes this one, so its role stays unknown here.
list_space_owners
Nowhere in Valuecase's article does this entry appear, and no source documents it. Like six other names here, it sits on the directory sheet with nothing attached. Any capability read into it would be a guess.
list_space_stakeholders
Valuecase describes adding stakeholders, not listing them, and no official text documents this name. The page leaves it undescribed rather than infer anything from the words it is made of.
set_task_assignees
Valuecase's list of task capabilities covers completion and due dates, and says nothing about assignees; no source documents this name either. Nothing more is written about it here.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping reviews open and closing edits, for example. That setting applies to everyone. Valuecase also points to the connector's settings in Claude to check your default tool permissions after connecting. And Claude works with your Valuecase rights and nothing more: a space you cannot open stays closed to it too.
Which plans it is available on
None of the 819 directory sheets shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens the connector for the organisation before members can connect individually. For the current state, check the Valuecase App sheet in the official directory. One more point: this connector is documented only by Valuecase itself, with no Claude help page of its own.
Where the Claude Valuecase App connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a buyer opens a room, submits a form or leaves a comment.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge 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 guarantee they behave as announced. Plug in only what comes from a publisher you trust. Other connectors are gathered on the Integrations hub.
Need help connecting Valuecase App to Claude?
A person reads every message.
