Customer Io
Server Details
MCP server for customer-io
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.1% over 22 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-customer-io
- GitHub Stars
- 0
- Server Listing
- mcp-customer-io
TDQS
Scored across 40 tools
Many tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all serve querying/discovery, and there are six polymarket edge/fill/arbitrage tools that heavily overlap. An agent will struggle to pick the right one without reading long descriptions.
Most tools use snake_case with some consistent prefixes (cio_, polymarket_, pipeworx_), but verb patterns vary widely (ask_, list_, get_, scan_, validate_, entity_profile, company_facts). The mix of verb-first and noun-phrase names creates a somewhat inconsistent feel, though not chaotic.
40 tools is a heavy surface for a server that mixes Customer.io operations, data lookup, prediction-market analysis, and memory. Many are meta-tools that could be consolidated (e.g., multiple ask_pipeworx variants, multiple polymarket edge detectors). The count exceeds typical well-scoped servers and adds selection overhead.
The server covers a wide domain: Customer.io metrics (campaigns, messages, segments), structured data lookup, prediction markets, memory, and utility tools. However, there are gaps—no create/update/delete operations for Customer.io campaigns, no direct action on most data sources beyond querying, and some tools (like generate_llms_txt) feel peripheral. The breadth is impressive but incomplete in lifecycle operations.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
40 tool updates
- First observed
ai_visibility_check - First observed
ask_pipeworx - First observed
ask_pipeworx_beta - First observed
ask_pipeworx_grounded - First observed
bet_research - First observed
cio_campaign_metrics - First observed
cio_list_campaigns - First observed
cio_list_messages - First observed
cio_list_segments - First observed
company_facts - First observed
compare_entities - First observed
deep_research - First observed
discover_tools - First observed
entity_profile - First observed
forget - First observed
generate_llms_txt - First observed
kalshi_weather_edge - First observed
list_subscriptions - First observed
pipeworx_feedback - First observed
pipeworx_trending - First observed
polymarket_arbitrage - First observed
polymarket_edge_tracker - First observed
polymarket_edges - First observed
polymarket_fill_risk - First observed
polymarket_kalshi_spread - First observed
recall - First observed
recent_alerts - First observed
recent_changes - First observed
release_calendar_markets - First observed
remember - First observed
resolution_audit - First observed
resolution_diff - First observed
resolve_entity - First observed
scan_competitor_ai_presence - First observed
scan_dependency - First observed
search_within - First observed
subscribe - First observed
suggest_questions - First observed
unsubscribe - First observed
validate_claim
Related MCP Connectors
MCP server for medicaid-intelligence
Related MCP Servers
- AlicenseAqualityAmaintenanceMCP server for Huly (task tracker) integration61,195 npm56MIT
- MIT
- AlicenseBqualityDmaintenanceMCP server for Maasy AI Marketing Copilot2171 npmMIT
- -
Glama MCP Gateway
Add one secure layer between your agents and this server.