CdpHub

Working Security A

com.cdphub/cdphubv1.0.3 Domain verified

Find which CDPs connect to your tools, compare CDP catalogs, and check a whole stack

Developer Tools

Watch Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://cdphub.com/functions/mcp

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

check_stack Read-only

Check a stack of two to ten tools against every CDP in CdpHub's directory, as the stack check on cdphub.com does: how many CDPs list all of them and which, those CDPs grouped by how they connect to each tool with each group counted, the CDPs that miss exactly one tool grouped by the tool they miss, and a link to the same check on cdphub.com. Use it for any question about two or more tools together, such as which CDPs fit a company's stack.

toolsarray, required

The tools, for example ["Shopify", "Klaviyo", "Snowflake"]: two to ten.

Tools (6)

check_stack

read-only

Argument	Type	Description
tools*	array	The tools, for example ["Shopify", "Klaviyo", "Snowflake"]: two to ten.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "tools"
  ],
  "properties": {
    "tools": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "minItems": 2,
      "description": "The tools, for example [\"Shopify\", \"Klaviyo\", \"Snowflake\"]: two to ten."
    }
  },
  "additionalProperties": false
}

compare_cdps

Compare two CDPs' integration catalogs in CdpHub's directory, tool by tool: how many tools both list, how many only one does, the most widely listed tools in both, each side's largest categories of tools the other lacks, and the link to their comparison page on cdphub.com.

read-only

Argument	Type	Description
a*	string	The first CDP, for example "Segment".
b*	string	The second CDP, for example "mParticle".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "a",
    "b"
  ],
  "properties": {
    "a": {
      "type": "string",
      "description": "The first CDP, for example \"Segment\"."
    },
    "b": {
      "type": "string",
      "description": "The second CDP, for example \"mParticle\"."
    }
  },
  "additionalProperties": false
}

get_cdp

Look up one customer data platform's integration catalog in CdpHub's directory: its number of tools and listings and its rank by catalog size, which way its integrations run, its largest categories with their most widely listed tools, how it connects to the main data warehouses, the CDPs that list the most of the same tools, and its page on cdphub.com.

read-only

Argument	Type	Description
name*	string	The CDP, for example "Segment", "Braze" or "Adobe Experience Platform".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "The CDP, for example \"Segment\", \"Braze\" or \"Adobe Experience Platform\"."
    }
  },
  "additionalProperties": false
}

get_tool

Look up one marketing or data tool (for example Snowflake, Braze, Google Ads or The Trade Desk) in CdpHub's directory: how many of the customer data platforms (CDPs) it tracks list an integration with it, each CDP counted once (both sends data to it and reads from it, only sends, only reads), which CDPs list it in each group and which don't, every listing with its direction, how it runs (server-side, client-side, in the warehouse) and a link to the CDP's own documentation, and the tool's page on cdphub.com. Use it for any question about one tool.

read-only

Argument	Type	Description
name*	string	The tool, for example "Snowflake" or "Google Ads".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "The tool, for example \"Snowflake\" or \"Google Ads\"."
    }
  },
  "additionalProperties": false
}

list_cdps

List every customer data platform in CdpHub's directory with its number of tools and listings and its page on cdphub.com, largest catalog first, with the directory's totals.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

search_directory

Search CdpHub's directory of CDP integrations by keyword, CDP, category, direction or how the integration runs. Returns the exact totals, the first results and the link to the same search on cdphub.com. Use get_tool for one named tool and check_stack for several.

read-only

Argument	Type	Description
cdps	array	Only these CDPs, for example ["Tealium"].
runs	array	How the integration runs: server-side, client-side, through a warehouse, or "none" when the listing doesn't say.
sort	string	The result order. Leave it out to let the directory decide.
group	string	Group the results by tool or by listing. Leave it out to let the directory decide.
query	string	Words to search for in tool, listing and CDP names, categories and descriptions, for example "reverse etl".
categories	array	Only these categories, for example ["Advertising"].
directions	array	Which way data moves, from the CDP's side: "out" sends data to the tool, "into" reads from it, "both", or "unknown" when the listing doesn't say.

Input schema (JSON)

CdpHub

Try it

check_stack Read-only

CdpHub

Try it

check_stack Read-only

Install

Tools (6)

Security checkA100/100