Valuecase App
Read, create and edit Valuecase digital sales rooms from an AI agent. Anthropic lists 35 tools; Valuecase documents capabilities but no tool names, and 14 of the 35 sit outside its written surface. OAuth with four real read/write scopes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Valuecase App via MCP
https://mcp.valuecase.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Valuecase App Tools & Capabilities (35)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Valuecase publishes no tool names. Its article documents 22 capability bullets across five sections and names none of the 35 tools, so every mapping on this page is a semantic match.
- Fourteen tools have no vendor documentation at all. The content-editing surface — including the connector's only delete — is undescribed, and Valuecase dates that feature as launching in August 2026. Expect this section to need re-checking; the vendor's article is the side that is behind.
templates:writeis advertised with no tool to use it. A scope naming a verb no tool carries is evidence of a surface not yet visible. It survived all three attribution tests.- Scopes do not separate the routine write from the irreversible one.
spaces:writecovers updating a property, posting a customer-visible comment, archiving a space and deleting content items alike. Consent is all-or-nothing within a scope. - Permanent space deletion is not available, by design. Valuecase states the MCP server supports archiving but provides no action for permanently deleting a space.
delete_content_itemsis a narrower thing, and Valuecase separately warns that a deleted page cannot be recovered. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here. In particular we cannot say whether
create_space_commenttakes a visibility or notification parameter, or whetheradd_space_stakeholderhas a flag that would change its notification behaviour. - Whether a specific task write emails the customer is unresolved. Valuecase makes it depend on per-space notification settings, and no tool in the listing reads those settings. Treat any task write on a live space as potentially customer-visible.
- Email-open tracking does not exist. Valuecase states it deliberately does not show email-open data, calling it unreliable. Engagement data covers what happened inside the space, not what happened in an inbox.
- The connector's tier changed recently. Our 2026-08-16 snapshot listed this entry as
community; the 2026-08-23 snapshot lists it aspartner, with the same endpoint and the same 35 tools. Only one Valuecase entry exists in the directory despite the-v2slug — there is no v1 listing at a different endpoint. - No rate limits are published. We found no statement of request limits for the MCP server in Valuecase's documentation.
Frequently asked questions
It can add a stakeholder, and Valuecase states adding one sends no invite. Its access-settings article says Valuecase will not send an email invite to your customers even when you add them by email, leaving customer conversations in your hands. But a stakeholder becomes a valid recipient of space notifications, and every notification email carries a link to the space.
Yes, through comments. Valuecase documents that mentions and replies are always enabled and cannot be disabled, so create_space_comment can reach an external stakeholder by email. Recipients can reply straight to that email and their reply posts back into the space thread. This is the connector's one confirmed outbound path to a person at another company.
Detailed behavioural data about named individuals. Valuecase tracks over 50 activity types including page visits, video plays, PDF views and file downloads, grouped into sessions carrying total time spent and visitor identity. Where a space restricts access by email, that activity is linked to a specific named person at the customer rather than recorded anonymously.
Anthropic lists 35. Valuecase publishes capability bullets rather than tool names, so no literal-string diff is possible. Fourteen of the 35 concern page, block and content editing, and Valuecase's own article describes editing spaces and templates as a coming feature launching August 2026 rather than a current one.
One tool carries a delete verb: delete_content_items. Valuecase's MCP article says permanently deleting Spaces is not available through the server, and archive_space is the documented alternative. That statement covers spaces, not content inside them, and Valuecase warns separately that a deleted page cannot be recovered.
Four, and they are real application scopes: templates:read, templates:write, spaces:read and spaces:write. Both the RFC 9728 resource descriptor and the authorization server advertised the same four on 2026-08-23. The boundary separates reading from writing, but not a routine write from an irreversible one.
No. Valuecase prices by seat and plan, not by consumption, so no single tool call spends credits or metered quota. Its published plans run from 59 euros monthly for Starter to 299 for Scale, with additional internal users charged separately. No tool in the surface reports usage or billing.
Admin access in Valuecase and an MCP-compatible client. Valuecase's article states that connecting requires Admin access, and that in Claude Team or Enterprise workspaces an owner or admin may need to add the connector before individual users can connect their own account. Sign-in is OAuth; do not put tokens in the URL.
Sources
- Valuecase MCP server help article (retrieved 2026-08-23). Appending
.mdto the article URL returns clean Markdown; we hashed that response against a known-bad article path and against the plain page to confirm it is a genuine route and not a shell. · retrieved 2026-08-23 - Valuecase, "Space access settings" (retrieved 2026-08-23) · retrieved 2026-08-23
- Valuecase, "Share a space with your customer" (retrieved 2026-08-23) · retrieved 2026-08-23
- Valuecase, "Stakeholder E-Mail Notifications FAQ" (retrieved 2026-08-23) · retrieved 2026-08-23
- Valuecase, "Managing Comments incl. Notifications" (retrieved 2026-08-23) · retrieved 2026-08-23
- Valuecase, "Tracking Customer Engagement with Activity Insights" (retrieved 2026-08-23) · retrieved 2026-08-23
- Valuecase, "How our engagement score works" (retrieved 2026-08-23) · retrieved 2026-08-23
- Valuecase, "Manage pages in a Space (or Template)" (retrieved 2026-08-23) · retrieved 2026-08-23
- Valuecase pricing (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: anonymous initialize returned HTTP 401 with a Bearer challenge naming the resource metadata document; RFC 9728 descriptor at
https://mcp.valuecase.com/.well-known/oauth-protected-resource/mcpand authorization server metadata athttps://mcp.valuecase.com/.well-known/oauth-authorization-server(2026-08-23). A control path under/.well-known/returned a distinct 404, so the 200s are genuine rather than a catch-all. · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Valuecase support — <mailto:support@valuecase.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Valuecase App
- Tools
- 35
- Domain
- mcp.valuecase.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.