Skip to main content
Glama

Server Details

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

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
CdpHub

TDQS

A4/5.0

Scored across 8 tools

Disambiguation4/5

Each tool maps to a distinct resource/action pair (one CDP, one tool, all CDPs, two CDPs, a multi-tool stack, a request check, a recipe, a keyword search), and descriptions actively route users (search_directory says to use get_tool for one tool and check_stack for several). The only mild overlap is get_api_recipe (produce a documented request) versus check_api_request (validate a request), which an agent could momentarily confuse, but the descriptions make the build-vs-check distinction clear.

Naming Consistency5/5

All eight names are snake_case verb_noun (check_*, get_*, list_*, search_*, compare_*) with no camelCase or bare-noun outliers. The verb choice is predictable: get_ for single-entity lookup, list_ for enumeration, check_ for validation, compare_ for pairwise analysis.

Tool Count5/5

Eight tools is squarely in the well-scoped range, and each one covers a distinct query shape (single entity, enumeration, pairwise, stack, request validation, recipe generation, search). Nothing looks redundant or padded.

Completeness4/5

Lifecycle coverage is strong for CDPs (list/get/compare/search, stack check, recipes, request validation). The notable gap is the lack of a list_tools counterpart to list_cdps, so an agent cannot enumerate the tool catalog directly and must infer it via search_directory or per-CDP lookups.

Publisher details

Operator
CdpHub, LLC · Publisher source
Operator website
https://cdphub.com
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Trust center
Not available
Restrictions
None: no sign-in, paid plan, admin approval or regional limit. · Publisher source

Available Tools

8 tools
check_api_requestCheck an API requestA
Read-onlyIdempotent
Inspect

Check an HTTP request for a CDP before you send it: is it a call the CDP's own developer docs document for one of five everyday jobs (send an event, create or update a profile, send a batch, look up a profile, delete a person), on a documented host, with the credential in a documented place and every required header, query parameter and body field? Uses the answer keys of CdpHub's agent readiness test, written by hand from each vendor's reference pages, for the 29 CDPs the test scored. It checks the request's form, not your data, and sends nothing to the vendor. Give the request as an object (method, url, headers, query, body) or as a curl command. Leave the job out to find the job it matches.

Inputs: cdp (required), job, curl, request.

check_stackCheck a stackA
Read-onlyIdempotent
Inspect

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, how they connect to each tool on its own with each group counted and a sentence for it, 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.

Inputs: tools (required).

compare_cdpsCompare two CDPsA
Read-onlyIdempotent
Inspect

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.

Inputs: a (required), b (required).

get_api_recipeGet an API recipeA
Read-onlyIdempotent
Inspect

The exact HTTP request a CDP's own developer docs give for an everyday job: send an event (send_event), create or update a profile (upsert_profile), send a batch of events (send_batch), look up a profile (read_profile) or delete a person (delete_user). Each request is written with one shared example (customer u_1001, ada@example.com, order ord_5001) and checked with the rules of CdpHub's agent readiness test; none was sent to the vendor's API. Where the CDP doesn't offer the job, or its docs couldn't be read, the answer says why. Covers the 30 CDPs in the agent readiness test and names the others. Placeholders in angle brackets are for the caller to fill in.

Inputs: cdp (required), job.

get_cdpLook up a CDPA
Read-onlyIdempotent
Inspect

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.

Inputs: name (required).

get_toolLook up a toolA
Read-onlyIdempotent
Inspect

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.

Inputs: name (required).

list_cdpsList the CDPsA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters.

search_directorySearch the directoryA
Read-onlyIdempotent
Inspect

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.

Inputs: cdps, runs, sort, group, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Hosted HTTP MCP server for B2B SaaS GTM stack research. 8 read-only tools wrapping stackswap.ai: search ~400 GTM tools, find curated overlaps (104 hand-verified pairs), suggest AI-native swaps (Outreach → Smartlead, ZoomInfo → Apollo), compare vendors head-to-head, run preview spend audits, get full tool profiles, get partner recommendations with implementation hours, and pull recommended starter
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides a context graph for GTM teams, centralizing data from multiple tools into unified person and company records, and offers MCP tools to retrieve account context, full entity details, and filtered queries.
      14 npm
      10
      AGPL 3.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Real-time B2B company firmographics, headcount tier, ARR estimate, tech stack adoption, and verified C-Level executive contact emails for AI SDRs and sales automation.
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources