Tenant accounts and people with firmographic, technographic, hierarchy, engagement, intent, and buying-group context; global B2B companies and contacts; and reference values such as industries, countries, and titles.
Demandbase One
Demandbase One is included for a vendor-hosted beta MCP that exposes five read-oriented tools across tenant account/person intelligence, global B2B company/contact directories, and reference metadata under existing Demandbase permissions.
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Search internal accounts or people, search the global company or contact directory, and retrieve reference data through the documented five-tool catalog. Results are governed by existing Demandbase permissions and requested record limits.
No MCP write tools were verified. The documented five-tool catalog is read-oriented across internal account/person search, global company/contact directories, and reference data.
Demandbase enablement is required. Custom clients use Dynamic Client Registration and OAuth Authorization Code with PKCE over Streamable HTTP, with an exact hosted HTTPS redirect URI allowlisted; retrieved data remains subject to existing Demandbase permissions.
MCP searches consume a shared organization credit pool per successfully returned record. Agent instructions require metadata-led tool selection, clarification of ambiguity, and explicit unsupported/out-of-scope errors rather than guessed fallback.
Beta and English-only; enablement is coordinated through the Demandbase account team; client support is limited to the documented list or approved custom-client flow; searches default to five and cap at 100 records; zero shared credits blocks calls.
Agent access
MCP support
Support: Official MCP server
Read scope: Five read-oriented tools cover internal account/person search, global company/contact search, and reference metadata; account lists are a filter on supported internal account search.
Write scope: No MCP write tools were verified. The documented five-tool catalog is read-oriented across internal account/person search, global company/contact directories, and reference data.
Authentication: OAuth Dynamic Client Registration with Authorization Code plus PKCE over Streamable HTTP; Demandbase must enable MCP and allowlist the exact hosted HTTPS redirect URI.
Approval boundary: The documented tools are read-oriented, so the primary confirmation boundary is cost and scope: show internal versus global search, filters, and requested result limit before a broad query that consumes shared credits.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Demandbase ships them.
Single-platform patterns
- ABM account journey and activation cockpit
- Account journey room
- Pipeline-quality debugger
- Customer expansion cockpit
Multi-platform compositions
- Demandbase One + marketing or intent platform: account journey room
- Demandbase One + conversation or support system + analytics or warehouse: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
8 recorded sources
First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Account-list support was added on 2026-06-22; the live catalog remains five read-oriented tools.
- Publisher published
- Jun 22, 2026
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
DCR, Authorization Code plus PKCE, endpoint discovery, Streamable HTTP, bearer tokens, enablement and exact redirect allowlisting are documented.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Jun 22, 2026
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP credit consumption and result-count limits
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
MCP credit consumption and result-count limits reviewed from live first-party material on 2026-07-22.
MCP tool-selection and error behavior
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
MCP tool-selection and error behavior reviewed from live first-party material on 2026-07-22.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.